In Scrum, we have what is called a burn down chart. This chart is a graphical representation of work that is left to do for the sprint iteration. It is often used in Agile software development. However, burn down charts can be applied to any project containing measurable progress over a period of time.
Typically, in a burn down chart, the outstanding work is often on the vertical y-axis, with the time along the horizontal x-axis. During the Daily Scrum, the development team updates the sprint’s burn down and determines the remaining work of the day. Truly Agile teams view the burn down chart as a “must” have tool because it helps monitor the project scope, keeps the team on task and assists in comparing the committed work in the sprint to the teams over-all progression.
The current Sprint progress is tracked using the burn down chart, the task board, and the daily scrum. In combination, these three things can provide a clear picture of what’s being worked on, what’s completed, what still needs to be done, and what might be preventing the team from meeting the sprint goal.
Sprint Review
At the end of each sprint, the team invites the stakeholders to a sprint review meeting where the features that were completed in the sprint are demonstrated to receive feedback. The Product Owner keeps track of the feedback and incorporates it as needed to the product backlog.
At the end of the Sprint Review session, the team conducts a Sprint Retrospective to determine what they did well, what they struggled with, and what recommendations they have for improvement going forward.
Leave a Reply
You must be logged in to post a comment.