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 functioningportal 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
You
are to divide into teams of 3 persons (or 2 or 4 persons if needed).
In a 3-person team, one person will assume each of the following
three roles: 1) Scrum Master – focus on process; 2) Product
Owner Coordinator – focus on the product (interfacing as needed
with the instructor who serves as Product Owner); 3) Developer Team
Coordinator – 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 membersand will rotate, as you see fit, for the following
Scenario 4. Reference the three 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. If for some reason, you are unable to work
productively as a team and divide and conquer work requirements, then
you will need to work individually, and each student will complete
all requirements.
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) Individual 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);
2.
Project Data Sheet (PDS) – Deliverables: 1) Group discussions in
the Workgroup Discussion forum; 2) Individual Project Data Sheet
Submitted (MS Word recommended);(Please see P105 of the PDF (agile
project management creating innovative products ch 6 PDS .pdf)
attached to this assignment for additional details.
1.
Agile PM Release Plan (for a 3-month project with 3 monthly sprints).
Deliverables:
1) Release plan and iteration discussions in the
Workgroup Discussion forum; 2) Release Plan (MS Word or MS PowerPoint
recommended);
2.
Team Building and Evaluation Narrative. In this narrative, you will
describe how your team came together or did not, and who did what,
including a rating of your team members and yourself according to
which criteria you think are important. Be sure to describe who did
the work products and how work assignments were decided. 1) Team
building posts in the Workgroup Discussion forum,
includingappropriate role playing (Scrum Master, Product Owner, or
Team Coordinator); 2) Team Buildingand Evaluation Narrative (MS
Word recommended). Note: A form is not provided. It’s up to you to
develop this narrative and /or table you think are appropriate.
Note:
Unless otherwise noted, all deliverables above are to be submitted
under Assignments. Each student is responsible for submitting his/her
own files/posts. For Scenario 3 and 4, deliverables may be
sharedamong actively participating team members. If team members are
not actively participating, contact the instructor and document as
part of your Deliverable #4 (Team Building and Evaluation
Narrative).If you need additional case facts,state your assumptions
and augment existing case details withadditionally compatible
details. It is my advice that you NOT share work products among
students not actively participating, but it’s your decision.
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.
Submit your assignment in your group’s discussion area.
Create a new post in your group’s discussion area called: “Final
Submission: Scenario 3” and attach the assignment deliverables to
that post by the assignment due date/time. You can submit the
Evaluation Narrative individually or as a team. If you elect to
submit the Evaluation Narrative individually, please submit it via
your individual assignment folder (“Project Scenario 3 Team
Building, Solution Building, and Release Management”) in LEO,
otherwise, it should be included in the post in your group discussion
area.
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 | Partial Points | No points | Possible Points | Points Earned |
|
Team building and Evaluation Exercise |
The response is per Agile principles and values, appropriate, well developed, and well presented with no errors in content or English usage. |
The response is not sufficiently per Agile principles/values, appropriate, or well developed and presented. |
No minimally acceptable presentation of value. |
25 | |
| Product Vision Exercise |
The response is per Agile principles and values, appropriate, well developed, and well presented with no errors in content or English usage. |
The response is not sufficiently per Agile principles/values, appropriate, or well developed and presented. |
No minimally acceptable presentation of value. |
25 | |
|
Project Data Sheet Exercise (Project Scope) |
The response is per Agile principles and values, appropriate, well developed, and well presented with no errors in content or English usage. |
The response is not sufficiently per Agile principles/values, appropriate, or well developed and presented. |
No minimally acceptable presentation of value. |
25 | |
| APM Release Plan Exercise |
The response is per Agile principles and values, appropriate, well developed, and well presented with no errors in content or English usage. |
The response is not sufficiently per Agile principles/values, appropriate, or well developed and presented. |
No minimally acceptable presentation of value. |
25 |
View
less »
Apr
29 2019 11:16 AM
1 Approved Answer
Peter
K answered
on September
28, 2019
5
Ratings, (9 Votes)
Group
4 Scenario 3 Release Plan for
U.S.
Homeland Security
Biohazard
Incident Tracking and Coordination System (BITCS)
Group
Members
UMUC
IFSM 441 6380
22
September 2019
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 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 | DURATION | STORY 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/ |
The post Purpose of the Assignment appeared first on My Assignment Online.