Kane Mar

The Enhanced (or Alternative) Release Burndown graph [1],[2] is a great tool and one of my personal favourites. It demonstrates several things very clearly. It demonstrates:

• The rate at which work is being completed by the team
• The rate at which new work is being added to the product backlog
• And, it can be used to determine a date range for completion.

Read the rest of this entry »

This first appeared on the ScrumAlliance.org website on October 30th. It is presented here in its original unedited form.

Burndown graphs are commonly used in Scrum projects to give the team an understanding of the amount of work remaining for the Sprint (or iteration). In Ken’s own words:

“As a team works together, it develop its own style of creating and maintaining the Sprint Backlog. It also demonstrates unique work patterns, some working consistently, some in bursts, some at the end of a Sprint. Some seek pressure, while others seek regularity. Across time, the backlog charts of each team develop predictable patterns. They stabilize as the team learns the technology, the business or product domain, and each other. These chart patterns are called Sprint signatures.” – ControlChaos.com [1]

Read the rest of this entry »