HOSTED BY: ALL STUDENTS
-Please note that Discussion 5 here is a continuation of Discussion 4 from last week and continues to prepare you for Scenario 3. Be sure you have located the MS Excel file named BITCS Backlog List. See in it the story summary information that you will need for developing your Release Plan in Scenario 3 and other deliverables in Scenario 4. Also, see below the Scenario 3 excerpt from our course syllabus that is attached here for your convenience.
PerDiscussion 5 requirements, you need to make one main post here in which you summarize comprehensively in 50+ words your understanding of the Scenario 3 requirements and, as well, ask your peer students for any advice on strategies, requirements, etc. that you may have. In effect, you should use other students in the class as a "Lifeline" to ask assistance and get guidance. Per standard requirements for conferences in this class, you should also have at least 2 peer postseither providing assistance or making comments.
21.Nov.2015 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. 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; 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, 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 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 Options: 1. Option 1: Submit ALL of the deliverables as a team in your team discussion area. Create a post called: "Final Submission: Scenario 3" and attach the assignment to that post. Make sure it's posted prior to the deadline! The assignment will be graded and feedback will be provided in the discussion forum and the grade will be applied to all of the team members. 2. Option 2: Submit item #4 (Team building and evaluation narrative) in your individual assignment folder (by the due date/time) and the remaining items using the method described above. Your team can pull out the "Team building and Evaluation Narrative" and submit this section individually; however, all of the other sections need to be submitted in the team's discussion area. If you choose this method - title your discussion post: "Final Submission: Scenario 3 - Excluding Item #4” Please note that if you choose this method and an individual does not submit item#4 in their individual assignment area, that individual will receive a zero for that portion of the assignment which is worth 25-points. If this option is selected, please ensure everyone turns in their individual submission. 3. NOTE: The results of the "Team building and Evaluation Narrative" can reduce individual grades if it's found there is low participation by a team member. 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 21.Nov.2015 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