Analyze a release
Agile Manager provides you with various analysis tools to track the progress and quality of a release.
Release Backlog page widgets
Use the widgets at the top of the Release Backlog page to review user story and defect statuses. The graphs refer to the items in the current filter.
On the Dashboard, select the predefined Release Manager Dashboard favorite. It includes the following widgets:
Displays the story points remaining to complete the release backlog, compared to the available capacity, at different stages of the release.
The straight diagonal line shows the remaining capacity (in hours) until the end of the release.
The curved line shows the hours of tasks remaining in the release.
- 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 number of story points completed by the group in each sprint, compared to the group's average sprint output.
Sprints with a velocity that was significantly different from the average may be worth further analysis.
Displays the number of defects assigned to the group, grouped by status, at different stages of the release. Each band shows the number of user stories in a status.
Following are the ideal trends you should see in these graphs and in each of their statuses:
In an ideal release, the shape of the graph should be almost rectangular, although there may be an increase of new items at the beginning of the release.
At the beginning of the release, 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||Most new content should be planned at the beginning of the release. Increases in the New band indicates user stories that were added during the release. 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 each sprint begins.|
|Done||The Done band should grow steadily throughout the release, until it dominates the graph by the end of the release.|
Displays the number of user stories and defects assigned to the group, grouped by status, at different stages of the release.
For a retrospective of the release planning, open the widgets gallery, and select widgets from the Retrospective category.
For a presentation of the release quality based on source code and build information, open the Release Management > ALI Summary page.