IFSM 441 SCENERIO 3 GRP
BYSTANDER
Group_4_IFSM_441_Scenerio_3_Release_Plan_FINAL.docx.pdf
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 1
Group 4 Scenario 3 Release Plan for
U.S. Homeland Security
Biohazard Incident Tracking and Coordination System (BITCS)
Shangyne Billups
Lydia Ewang
Charles Hudgens
Melanie Reagin
Gary Waguespack
UMUC IFSM 441 6380
22 September 2019
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 2
Release Plan for U.S. Homeland Security
Biohazard Incident Tracking and Coordination System
XYZ Corporation has been contracted by the U.S. Department of Homeland Security
(DHS) to develop and implement a Biohazard Incident Tracking and Coordination System
(BITCS). The requirements of the contract prescribed an Agile software development and project
management implementation methodology. The timeline for full delivery is twelve (12) months;
with a functioning portal required within four (4) months and the fully integrated application and
database fully functional within the following eight (8) months of development.
Release Plan
Following the Agile Project Management (APM) delivery framework, a release plan has
been developed based on the BITCS backlog list of stories provided by DHS, Product Owner.
The total project backlog is estimated at 3,125 hours of labor. The estimated time allotted for a
functional release has been projected to be four (4) months. The BITCS backlog list is located in
Appendix A.
The XYZ APM Team has grouped the backlog listing into four iterations. Each iteration
is a sprint and each sprint will last four weeks in duration. At the conclusion of each sprint,
deliverables will be released. Details of the iterations are outlined in the release plan. The
release plan provides a better understanding of the projects viability and feasibility.
The initial release of the BITCS will contain requirements of highest priority and
customer value from the backlog list and are included as stories in the first sprint. Priorities are
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 3
addressed in descending order as release plans and iterations progress (Dash, 2018, para. 15).
Release 4, the final release will be at the conclusion of the 4th sprint and will deliver a completed
product containing all requirements listed in the initial backlog. The end state of the four (4)
month project will be an operable biohazard incident portal. The complete release plan is below.
SPRINT
Release TASK NAME
FEATURE
TYPE START FINISH
DURATI
ON
STOR
Y ID
STORY DEP #S
REQUIREMENT RELEASE DATE GOAL
1 Mobile Device
Implementation
Technical
Domain 10/7/2019 11/1/2019
200
hours 1 0 11/4/2019
Minimum Viable Product
(MVP)
1
Intranet/Internet
Network Hardware
(HW)
Technical
Domain 10/7/2019 11/1/2019
200
hours 2 1 11/4/2019
Minimum Viable Product
(MVP)
1
Install and configure
network software
(SW), etc.
Technical
Domain 10/7/2019 11/1/2019
100
hours 3 1, 2 11/4/2019
Minimum Viable Product
(MVP)
1
Communication
infrastructure QA
and testing
Technical
Domain 10/7/2019 11/1/2019
100
hours 4 1, 2, 3 11/4/2019
Minimum Viable Product
(MVP)
1
Install/configure
Server O/S
(Windows Server)
Technical
Domain 10/7/2019 11/1/2019
100
hours 5 1, 2, 3, 4 11/4/2019
Minimum Viable Product
(MVP)
1 Install/configure
SharePoint
Technical
Domain 10/7/2019 11/1/2019
100
hours 6 1, 2, 3, 4, 5 11/4/2019
Minimum Viable Product
(MVP)
2 Install/configure CIA
Package XYZ-231
Technical
Domain 11/4/2019 12/6/2019
50
hours 7
1, 2, 3, 4, 5,
6 12/9/2019
Functioning Biohazard
Portal
2 Install/configure
SQL Server
Technical
Domain 11/4/2019 12/6/2019
100
hours 8
1, 2, 3, 4, 5,
6, 7 12/9/2019
Functioning Biohazard
Portal
2
Install/configure
connectivity SW &
do QA
Technical
Domain 11/4/2019 12/6/2019
100
hours 9
1, 2, 3, 4, 5,
6, 7, 8 12/9/2019
Functioning Biohazard
Portal
2
Install/configure
security SW/HW &
do QA
Technical
Domain 11/4/2019 12/6/2019
200
hours 10
1, 2, 3, 4, 5,
6, 7, 8, 9 12/9/2019
Functioning Biohazard
Portal
2
Install/configure
developer HW/SW
stations & access
Technical
Domain 11/4/2019 12/6/2019
100
hours 11
1, 2, 3, 4, 5,
6, 7, 8, 9, 10 12/9/2019
Functioning Biohazard
Portal
2 Install XYZ
Corporation
Biohazard Portal
Technical
Domain
11/4/2019 12/6/2019 100
hours
12 1, 2, 3, 4, 5,
6, 7, 8, 9, 10,
11
12/9/2019 Functioning Biohazard
Portal
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 4
SPRINT
Release TASK NAME
FEATURE
TYPE START FINISH
DURATI
ON
STOR
Y ID
STORY DEP #S
REQUIREMENT RELEASE DATE GOAL
(Build 21Q)
2
Field Bio-hazard
Team Work Package
Interface
Customer
Domain 11/4/2019 12/6/2019
150
hours 13 1--12 12/9/2019
Functioning Biohazard
Portal
3
Central
Dispatcher/Observe
r Interface
Customer
Domain 12/9/2019 1/10/2020
100
hours 14 1--12, 13 1/13/2020
Functioning Mobile Case
Management System w/
required interfaces
3
XYZ C Mobile Case
Management
System (Build 11C)
Customer
Domain 12/9/2019 1/10/2020
300
hours 15 1--12, 13, 14 1/13/2020
Functioning Mobile Case
Management System w/
required interfaces
3
Custom Lab
Application Data
Input Interface
Customer
Domain 12/9/2019 1/10/2020
100
hours 16 1--12, 13, 14 1/13/2020
Functioning Mobile Case
Management System w/
required interfaces
3
Custom Lab
Application Data
Results Access
Interface
Customer
Domain 12/9/2019 1/10/2020
100
hours 17 1--12, 13, 14 1/13/2020
Functioning Mobile Case
Management System w/
required interfaces
3
Custom Emergency
Communications
Interface
Customer
Domain 12/9/2019 1/10/2020
150
hours 18 1--12, 13, 14 1/13/2020
Functioning Mobile Case
Management System w/
required interfaces
4
Custom CIA/NSC
Bio-hazard Interface
& Data Access
Customer
Domain 1/13/2020 2/7/2020
200
hours 19 1--12, 13, 14 2/10/2020 Complete BITCS
4
Custom Public
Health Information
Interface
Customer
Domain 1/13/2020 2/7/2020
50
hours 20 1--12, 13, 14 2/10/2020 Complete BITCS
4 Custom Biohazard
Mobile Field Log
Customer
Domain 1/13/2020 2/7/2020
125
hours 21 1--12, 13, 14 2/10/2020 Complete BITCS
4
Custom Field Bio-
hazard Team
Interaction
Application
Customer
Domain 1/13/2020 2/7/2020
250
hours 22 1--12, 13, 14 2/10/2020 Complete BITCS
4 Custom Utility
Package
Customer
Domain 1/13/2020 2/7/2020
50
hours 23 1--12, 13, 14 2/10/2020 Complete BITCS
4 QA for Fully Functional
Portal per Specs
Technical
Domain 1/13/2020 2/7/2020
100
hours 24
1--12, 13,
14--23 2/10/2020 Complete BITCS
Figure 1: BITCS Release Plan
Conclusion
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 5
The release plan is an organic document and will be maintained by the AGM Team. It is
intended to serve as XYZ Corp.’s navigating device to achieving the product’s successful
delivery within the established constraints (Dash, 2018, para. 14). Delivering the greatest value
to the customer is the AGM Teams goal. As such, the release plan is subject to evolve with the
needs of the client. Changes to the backlog can be incorporated and ranked into proper position
for future iterations if newer features take priority.
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 6
References
Dash, S. N. (2018, December 5). Agile Release Planning: Let's Break It Down! Retrieved from https://www.mpug.com/articles/agile-release-planning-lets-break-it-down/
Table of Figures
Figure 1: BITCS Release Plan………………………………………………………... Page 3
Figure 2: BITCS Backlog List. ………………………………………………………..Page 7
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 7
Appendix A
BITCS Backlog
Story ID
Name Description Story Type EstWo rkHrs
1 Mobile Device Implementation
Mobile device HW & SW installation/configuration
Technical Domain
200 hours
2 Intranet/Internet Network Hardware (HW)
Network infrastructure HW, cabling, wireless, etc.
Technical Domain
200 hours
3 Install and configure network software (SW), etc.
Network software for included hardware (routers, etc.)
Technical Domain
100 hours
4 Communication infrastructure QA and testing
Communication infrastructure QA and testing
Technical Domain
100 hours
5 Install/configure Server O/S (Windows Server)
Install/configure Server O/S (Windows Server)
Technical Domain
100 hours
6 Install/configure SharePoint Install/configure SharePoint, etc.
Technical Domain
100 hours
7 Install/configure CIA Package XYZ-231
Install/configure CIA Package XYZ-231 (Top Secret)
Technical Domain
50 hours
8 Install/configure SQL Server
Install/configure SQL Server Technical Domain
100 hours
9 Install/configure connectivity SW & do QA
Install/configure connectivity SW & do QA
Technical Domain
100 hours
10 Install/configure security SW/HW & do QA
Install/configure security SW/HW & do QA
Technical Domain
200 hours
11 Install/configure developer HW/SW stations & access
Install/configure developer HW/SW stations & access
Technical Domain
100 hours
12 Install XYZ Corporation Biohazard Portal (Build 21Q)
Install XYZ Corporation Biohazard Portal (Build 21Q)
Technical Domain
100 hours
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 8
Story ID
Name Description Story Type EstWo rkHrs
13 Field Bio-hazard Team Work package Interface
Field Bio-hazard Team Work package Interface
Customer Domain
150 hours
14 Central Dispatcher/Observer Interface
Central Dispatcher/Observer Interface - Control
Customer Domain
100 hours
15 XYZ C Mobile Case Management System (Build 11C)
XYZ C Mobile Case Management System (Build 11C)
Customer Domain
300 hours
16 Custom Lab Application Data Input Interface
Custom Lab Application Data Input Interface
Customer Domain
100 hours
17 Custom Lab Application Data Results Access Interface
Custom Lab Application Data Results Access Interface
Customer Domain
100 hours
18 Custom Emergency Communications Interface
Custom Emergency Communications Interface
Customer Domain
150 hours
19 Custom CIA/NSC Bio- hazard Interface & Data Access
Custom CIA/NSC Bio-hazard Interface & Data Access
Customer Domain
200 hours
20 Custom Public Health Information Interface
Custom Public Health Information Interface
Customer Domain
50 hours
21 Custom Biohazard Mobile Field Log
Custom Biohazard Mobile Field Log
Customer Domain
125 hours
22 Custom Field Bio-hazard Team Interaction Application
Custom Field Bio-hazard Team Interaction Application
Customer Domain
250 hours
23 Custom Utility Package Custom Utility Package Customer Domain
50 hours
24 QA for Fully Functional Portal per Specs
QA for Fully Functional Portal per Specs
Technical Domain
100 hours
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/
GROUP 4 SCENARIO 3 RELEASE PLAN FOR BITCS 9
Figure 2: BITCS Backlog List
This study source was downloaded by 100000785772547 from CourseHero.com on 10-31-2022 09:49:42 GMT -05:00
https://www.coursehero.com/file/47208168/Group-4-IFSM-441-Scenerio-3-Release-Plan-FINALdocx/ Powered by TCPDF (www.tcpdf.org)
