It might seem that software development and predictable results go together like fire and water—which is to say, not at all. Your developers might hit unexpected snags, productivity varies between Sprints, and it’s difficult to say how much exactly will be done, and when.
But it doesn’t have to be that way.
Introducing: burndown charts.
A burndown chart enables the monitoring of work progress in a Sprint and product release by clearly visualizing the difference between the actual and predicted effort.
Burndown charts are useful in:
In Scrum, 2 types of burndown charts are usually used: a Sprint Burndown chart and a Product Burndown chart. The difference between them lies in the time range and ownership.
A Sprint Burndown chart is used by the Development team within one Sprint to monitor work progress, while a Product Burndown chart is used by the Product Owner for product management purposes.