Sprint burndown chart
I have been creating a sprint burndown chart manually every day using a Google spreadsheet. Attached is an example (with fake data).
I hang it on our bulletin board daily above our espresso machine next to an old picture of a Pivotal mustache contest. Hee hee.
This chart keeps our sprint progress visible to anyone who is interested.
Maybe something like this could be built into Tracker someday?
I hang it on our bulletin board daily above our espresso machine next to an old picture of a Pivotal mustache contest. Hee hee.
This chart keeps our sprint progress visible to anyone who is interested.
Maybe something like this could be built into Tracker someday?
12
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Hi Heidi....we have a story for a better burndown chart in our backlog, but this example definitely helps solidify what it should look like. Thanks for posting it!
-
Inappropriate?By the way, Google autoassigns the colors in the chart and you can't change them. You could choose better color mapping to the different states. It might also be nice to hover over a color on a particular day, like the delivers on 6/17 and get the number of points that are in that state. But those are extras.
-
Inappropriate?Hi Heidi,
It's not exactly what you're looking for, but have you seen the "Current Iteration Burn-up Chart" in the charts tab? It shows how you're progressing in the current iteration compared with the expected progress given your velocity. -
Inappropriate?Hi - I've seen that. It's a nice chart but it doesn't get granular enough for us to use it.
Some type of visual way to identify clogs or bottlenecks in our system is what we need so we can try to fix things during the sprint - before our sprint is over.
If we can see, for example, that a lot of stories remain each day in deliver state we can have a discussion about how to speed up our qa delivery process (which is what we use the deliver state for). So then we can try to course correct and keep things moving.
Or maybe some stories stay in accept/reject too long and we need to speed that up to get quicker feedback from our product owner. (We have one person who goes through stories in accept/reject all during the sprint).
And sometimes there is a need to add stories during a sprint. Bringing visibility to that can be really powerful since there is a cost to adding points.
We can get this type of info by looking at the Current column in tracker each day, but to be able to see this for a period of days helps us get the bigger picture so we can take action and meet the goal we set a the beginning of the sprint before it's too late. -
Inappropriate?Heidi, I love it and showcased your chart to many people in our company. If there's anyway I can get a copy of the actual spreadsheet, that'd be awesome! If not, totally understand.
Notes to Pivotal: if you implement something like this, what would be helpful is also some way to display which stories were added or moved out of the release. I'd also like this chart based on each iteration instead of release if possible.
I’m inspired!
-
Inappropriate?Hi YY I didn't notice this until now. Tell me your email address and I can share the googledoc with you.
-
hi heidi! can you please email me a copy of your 'sprint burndown chart'? jonathannelson@yahoo.com thanks! -
Inappropriate?I would love a copy of the googledoc also, if you could send it over, i would appreciate it. Thanks!
Dick
dick.mcmullen@csu.mnscu.edu -
Inappropriate?Hi Heidi, could you please send to me please marcello.sales@gmail.com!!! Your example will help me a lot with my grad school research...Thanks!!!
I’m excited
-
Inappropriate?Hi Heidi, this sounds like just what I'm looking for! Any chance you could share it with my hotmail account - "rubbish_dan" ?
Best regards,
Dan -
Inappropriate?I would love a copy too: pdelre.work@gmail.com. Thank you.
Loading Profile...




EMPLOYEE
EMPLOYEE



