HOSTED BY: GROUP 4
-In Scenario 3, you were required to develop a release plan for the first four months of a year-long project (or the full year,
depending on your interpretation)
. Scenario 4 continues Scenario 3, but shifts from the high-level release level to the low-level estimation, sprint backlog, daily Scrum meeting, sprint burndown, and release burndown "rubber meets the road" level. You have two weeks to complete Scenario 4. Be sure you read over Scenario 4 carefully several times.
This week's activities helps get you and your team focused on coming up to speed on some of the main concepts and practices you will need to master in Scenario 4. Your most helpful resources will be the Lecture Notes, assigned readings, and any additional web resources you may search out and choose to use.
For Discussion 6, the requirement is to develop a 100+ word post that summarizes the 3 main ways that sprint work efforts (workload) can be estimated from user stories: function points, storypoints, and estimated hours. Keep in mind that you will be using estimated hours (as provided) for Scenario 4 purposes.
Note:The knowledge and insight you gather from this review will be helpful for you in completing the exercises (parts) of Scenario 4. This Scenario 4, in a sense, culminates the planning/execution work cycle because Scenario 5 focuses on retrospectives, or looking back at what has been done and how it could have been done better. Scenario 4 is focused on giving students a first-hand insight into how work tasks (features) are developed within an Agile PM project.
Note: Content not coming directly from you will need to be cited per APA. FYI, best practice is to use citations to support your content and assertions.
Note: Responses may be a single paragraph or multi-paragraph, but should be well-organized, thorough, and well-presented.