Project Scenario 3 Team Building, Solution Building, and Release Management

Story ID
Name
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Mobile Device Implementation
Intranet/Internet Network Hardware (HW)
Install and configure network software (SW), etc.
Communication infrastructue QA and testing
Install/configure Server O/S (Windows Server)
Install/configure SharePoint
Install/configure CIA Package XYZ-231
Install/configure SQL Server
Install/configure connectivity SW & do QA
Install/configure security SW/HW & do QA
Install/configure developer HW/SW stations & access
Install XYZ Corporation Biohazard Portal (Build 21Q)
Field Bio-hazard Team Workpackage Interface
Central Dispatcher/Observer Interface
XYZ C Mobile Case Management System (Build 11C)
Custom Lab Application Data Input Interface
Custom Lab Application Data Results Access Interface
Custom Emergency Communications Interface
Custom CIA/NSC Bio-hazard Interface & Data Access
Custom Public Health Information Interface
Custom Biohazard Mobile Field Log
Custom Field Bio-hazard Team Interaction Application
Custom Utility Package
QA for Fully Functional Portal per Specs
BITCS – Biohazard Incident Tracking & Coordination System
Description
StoryType
Mobile device HW & SW installation/configuration
Network infrastructure HW, cabling, wireless, etc.
Network software for included hardware (routers, etc.)
Communication infrastructue QA and testing
Install/configure Server O/S (Windows Server)
Install/configure SharePoint, etc.
Install/configure CIA Package XYZ-231 (Top Secret)
Install/configure SQL Server
Install/configure connectivity SW & do QA
Install/configure security SW/HW & do QA
Install/configure developer HW/SW stations & access
Install XYZ Corporation Biohazard Portal (Build 21Q)
Field Bio-hazard Team Workpackage Interface
Central Dispatcher/Observer Interface – Control
XYZ C Mobile Case Management System (Build 11C)
Custom Lab Application Data Input Interface
Custom Lab Application Data Results Access Interface
Custom Emergency Communications Interface
Custom CIA/NSC Bio-hazard Interface & Data Access
Custom Public Health Information Interface
Custom Biohazard Mobile Field Log
Custom Field Bio-hazard Team Interaction Application
Custom Utility Package
QA for Fully Functional Portal per Specs
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Technical Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Customer Domain
Technical Domain
EstWorkHrs
StoryDep#sReq
200 hours
200 hours
100 hours
100 hours
100 hours
100 hours
50 hours
100 hours
100 hours
200 hours
100 hours
100 hours
150 hours
100 hours
300 hours
100 hours
100 hours
150 hours
200 hours
50 hours
125 hours
250 hours
50 hours
100 hours
0
1
1, 2
1, 2, 3
1, 2, 3, 4
1, 2, 3, 4, 5
1, 2, 3, 4, 5, 6
1, 2, 3, 4, 5, 6, 7
1, 2, 3, 4, 5, 6, 7, 8
1, 2, 3, 4, 5, 6, 7, 8, 9
1, 2, 3, 4, 5, 6, 7, 8, 9, 10
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
1–12
1–12, 13
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14
1–12, 13, 14–23
Scenario #3 (Team Building, Solution Building, and Release
Management–Group Project)
UMUC IFSM 441
Scenario 3: Team Building, Solution Building, and Release Management
Due Week 5
Introduction
Before you begin this assignment, be sure you have read the seminal “XYZ Corporation Case”.
Purpose of the Assignment
This assignment gives students the opportunity to apply IFSM 441 course concepts and
specifically addresses the following course outcomes:
1. Evaluate the values, principles, strategies and practice of Agile tools in order to mitigate
uncertainty and risk with project delivery.
2. Compare Agile versus traditional project methodologies in order to provide thebest fit for
the organization.
3. Apply Agile framework to meet the specific operational needs.
Scenario #3 Group/Individual Assignment Extension to Main Case
Internal/External: External project for the Health Crisis Prevention and Response Management
Service/Product Delivery Division.
Project Title: U.S. Homeland Security Biohazard Incident Tracking and Coordination System
(BITCS).
Brief Description: XYZ has just won a contract with the federal government to put in place a
state-of-the-art Biohazard Incident Tracking and Coordination System portal and applications for
collaboration between emergency responders and for decision support. BITCS is an Intranet-only
accessible portal (for facilitating collaboration) with seamless access to event data relating to
active biohazards.
Other Key Information: XYZ Corporation’s winning bid response specifications call for largely
Microsoft technologies, including SharePoint (portal), SQL Server (database platforms), .NET
(backend application and client application architecture and technology), and MS Office
(desktop knowledge worker facilitation). The Homeland Security unit procuring the application
prescribed an Agile software development and project management solution, so XYZ responded
accordingly. Your Agile Team has been assigned with team building, product development, and
release plan responsibilities (Scenario 3, this scenario), followed later by sprint plan development
and exploration (execution of development tasks). Due to the requirements of the client, this
engagement is expedited. The timeline for full delivery is 1 year but after 4 months a functioning
portal is required under the awarded contract. After 8 months the application and databases
deliverables are due. After 1 year, the fully delivered integrated solution (portal working with
applications/databases) is due.
Your Group and Assigned Roles
This is a Group/Team Assignment:
One or more members from your Group will assume each of the following roles:
1) Scrum Master – focus on process;
2) Product Owner;
3) Product Owner Coordinator – focus on the product (interfacing Product Owner);
4) Developer Team Coordinator 1 – focus on the developer team inputs (you represent the voices
of 11 developer team members (including 2 .NET developers, 2 SQL Server developers, 2
SharePoint developers, 2 quality assurance specialists testers, 2 business analysts, and 1 technical
writer).
Your roles within the team for Scenario 3 will be self-determined by the team members and will
rotate, as you see fit, for the following Scenario 4. Reference the Scrum/Agile roles in the
Lecture Notes and in assigned readings for more role details. Aside from your assigned role, you
should self-organize and share responsibilities to help your team meet its assignment
requirements, sharing the workload as equally as is feasible.
Overview of Scenario #3 Task Assignment
Refer to the News post from the instructor and use the Lecture Notes and assigned readings to
better understand assignment requirements that follow. Your task assignment is to develop for
this Agile project scenario four deliverables:
1. Product Vision (Vision Box & Elevator Test Statement) – Deliverables: 1) Group
discussions in the Workgroup Discussion forum; 2) Product Vision PowerPoint
Submitted (MS PowerPoint recommended) (4-slide presentation of the front, back, and
left side, and right side of a box (with no top and bottom); 3) Another slide with the
Elevator Test Statement; Sample Vision Box: Importance of Product Vision in Scrum •
Tuleap
2. Project Data Sheet (PDS) – Deliverables: 1) Group discussions in the Workgroup
Discussion forum; 2) Project Data Sheet Submitted (MS Word recommended);(Please see
P105 of the PDF (Agile Project Management Creating Innovative Products.pdf) attached
to this assignment for additional details.
3. Agile PM Release Plan (for a 4-month project with 4 monthly sprints). Deliverables:
1) Release plan and iteration discussions in the Workgroup Discussion forum; 2) Release
Plan (MS Word or MS PowerPoint recommended);
4. Team Building and Evaluation Narrative. In this narrative, you will describe how your
team came together or did not, and who did what and an overall score for each team
member. Be sure to describe who did the work products and how work assignments were
decided. 1) Team building posts in the Workgroup Discussion forum, including
appropriate role playing (Scrum Master, Product Owner, or Team Coordinator); 2) Team
Building and Evaluation Narrative (MS Word recommended). Note: A form is not
provided. It’s up to you to develop this narrative and /or scoring table you think are
appropriate. However, each team member needs to use the same scoring method and
table as determined by the team. Note: You will reuse the scoring method/table for
Scenario #4.
Task Requirements
1. Submit appropriate content under #1-#4 in the preceding list as separate or consolidated
files to meet Scenario 3 requirements;
2. Follow the approaches, methodologies, conventions, and formats presented in Lecture
Notes and assigned readings unless otherwise directed by the instructor;
3. You are encouraged to interact actively in your Workgroup Discussion forum and your
posts there may make up part of your Scenario 3 grade – if you want to, you may also
interact with your workgroup in other ways (email, Pager, telephone, etc.) as needed to
get the job done.
4. Follow all guidelines in the provided assignment rubric to maximize your grade; and
5. Submission Instructions: Select 1 member from the Group/Team to submit all of the
deliverables on behalf of the Group/Team. Be sure to indicate on the cover page and
within the titles of each deliverable, the Group number (e.g…Group 2, Group 4…)
Other Guidance
See the Course Syllabus, related Course Content area files, and LEO Classroom News as needed
for supporting information.
Scenario #3 Grading Rubric
Attribute
Full Points
Team building The response is
and Evaluation per Agile
Exercise
principles and
values,
appropriate, well
developed, and
Partial Points
No points
The response is No minimally
not sufficiently acceptable
per Agile
presentation of
principles/values, value.
appropriate, or
well developed
Possible
Points
25
Points
Earned
well presented
and presented.
with no errors in
content or English
usage.
Product Vision The response is
The response is No minimally
Exercise
per Agile
not sufficiently acceptable
principles and
per Agile
presentation of
values,
principles/values, value.
appropriate, well appropriate, or
developed, and
well developed
well presented
and presented.
with no errors in
content or English
usage.
25
Project Data
The response is
The response is No minimally
Sheet Exercise per Agile
not sufficiently acceptable
(Project Scope) principles and
per Agile
presentation of
values,
principles/values, value.
appropriate, well appropriate, or
developed, and
well developed
well presented
and presented.
with no errors in
content or English
usage.
25
APM Release
Plan Exercise
25
The response is
The response is No minimally
per Agile
not sufficiently acceptable
principles and
per Agile
presentation of
values,
principles/values, value.
appropriate, well appropriate, or
developed, and
well developed
well presented
and presented.
with no errors in
content or English
usage.