Agile → Overview → Products, Releases, Sprints, and Teams → Releases → Release Burndown
A Burndown chart is a simple way of measuring a team's progress during a sprint by comparing the working days in the sprint to the total number of story points to which the team committed. A story is considered complete when it has zero story points remaining and has been accepted by the product owner. A sprint can be considered complete when the total story points to which the team committed reaches zero. Ideally, this occurs on the last working day of the sprint. Working days in a sprint are defined by the working days in your organization's company calendar.
Burndown charts can be useful at several points within the agile lifecycle: during a release, during a sprint, and for a specific task. A release Burndown is useful for tracking the progress of a release by using a single metric (such as total story points remaining or total work hours remaining) and comparing it against the original total toward which the team has made a commitment. As team members update this metric for the individual work items they are assigned, the release Burndown chart is updated to show the overall progress of the team.
Serena Agile On Demand includes an out-of-the-box release burndown chart as part of the Tracking module. The release burndown is used to view the current status of the release. The list of work items, sorted by sprint will appear in the related backlog pane. Out-of-the-box burndown charts will show the backlog from which the burndown chart is based as part of the release, sprint, and task burndown views.
Copyright © 2003–2009 Serena Software, Inc. All rights reserved.