Track and analyze the sprint
Agile Manager provides you with a variety of analysis tools to use during your daily scrum meetings and at the sprint retrospective.
Sprint retrospective tools
- Use the widgets at the top of the Release Management > Sprint Closure page for a summary of the sprint.
- On the Dashboard, select widgets from the Retrospective category.
Daily sprint tracking
At the daily scrum meetings, use the Scrum Master Dashboard for an up-to-date snapshot of the sprint. It includes the following widgets:
Displays the work remaining to complete the team’s sprint backlog, compared to the available team capacity, at different stages of the sprint.
The straight diagonal line shows the remaining team capacity (in hours) until the end of the sprint.
The curved line shows the hours of tasks remaining in the sprint.
- If the curved line is higher than the straight line, the team is behind schedule.
- If the curved line is lower than the straight line, the team is ahead of schedule.
Displays the flow of the sprint's user stories through the different statuses, along the sprint time line. Each band shows the number of user stories in a status.
Following are the ideal trends you should see in the graph and in each of its statuses:
|Total||In an ideal sprint, the shape of the graph should be almost rectangular. At the beginning of the sprint, the graph's height is made up primarily of new items. From that point on, the planned items move through the different statuses, until they are all done.|
|New||All new content should be planned by the beginning of the sprint. An increase in the New band means that user stories were added during the sprint. The band should gradually get narrower as user stories move to In Progress.|
|In Progress||The number of In Progress user stories should be more-or-less constant. The team should be closing up user stories, and moving them to In Testing, before starting work on additional items.|
|In Testing||The progress of the In Testing band should mirror the In Progress band, with a slight time lag. To ensure a gradual flow of items from In Progress to In Testing, the team should attempt to complete several small user stories shortly after the sprint begins.|
|Done||The Done band should grow steadily throughout the sprint, until it dominates the graph by the end of the sprint.|
Displays the number of story points completed by the team in the previous sprints, and in the current sprint to-date, compared to the team’s average sprint output.
Displays the work remaining in the sprint for individual team members, compared to the member’s remaining capacity.