Sprint Backlog
Spring Backlog Exercise – The gist of this exercise is to survey and define the sprint backlog. See background information in Lecture Notes, assigned readings, and your own web searches.
Exercise 2 (Sprint Backlog) Context
As noted in the “Sprint Backlog” section of the Webliography document Do Better Scrum, the purpose of the sprint backlog is to tell the whole team and anyone else what work they have planned for the sprint and their current status. The time context for this exercise is just before the sprint begins. While this Exercise 2 follows generally in a time context after Exercise 1, the Exercise 1 information is not relevant here for the purposes of Exercise 2.
Exercise 2 Overview
In this exercise, you will use the data in the Scenario 4 BITCS Product Backlog file to devise a part of a sprint backlog file. In particular, you will build only the part of the sprint backlog that relates to StoryID 21 (Custom Biohazard Mobile Field Log). The purpose of this story is to develop a field log for gathering empirical data on potential biohazards identified in the field. The full story text follows: As a team member, I can record the key data on potential biohazards identified during field incident deployment. See the following link for helpful related details on the contents of sprint backlogs, and, as a tip, note what is contained in these typical entries for a story:
http://www.mountaingoatsoftware.com/scrum/sprint-backlog
Exercise 2 Background Metrics
– Team Makeup/Size: No need to consider for the purposes of this exercise
– Number of Total Team Hours to Execute This Story (per the spreadsheet): 125
– Number of Tasks Expected by the Course Instructor: 3-6
– Number of Work Days to Execute This Story: 5
Exercise 2 Requirements
Using the sprint backlog at the link above as your guide, develop a similar MS Word table to serve as the sprint backlog excerpt in this exercise. You will need to use your imagination and/or systems analysis expertise to develop the individual tasks relating to this story. The link above will give you some ideas on how the story may be broken into tasks. Likewise, using your imagination and/or systems analysis expertise, you will need to make an estimate of the daily breakdown of hours to get to the total of 125 at the end of the prescribed 5 days allowed for executing this story. I recommend adding a refinement to the link example: totaling your estimated hours for the day and week. Remember, as stated, above, the time context is before the start of the sprint, so this is actually an estimate.
