I've recently started to wonder if a burndown based on story points is very much helpful?
In the future when we estimated only subtasks using story points, the burndown told me that we burned story points, and the guideline told me if we were on or off target.
Now, moving to rapid boards, we start to estimate the stories using story points and the sub-tasks using hours. So we end up with a burndown of story points similar to this, https://confluence.atlassian.com/display/AGILE/Viewing+the+Burndown+Chart, that doesn't ease my mind as project manager until the last day of the sprint.
I get that the burndown of hours will provide me with at least knowledge that people are working. And a report of estimates vs. logged hours can indicate if we are spending more or less time then expected. But what does the burn down of story points really give me? Can anyone help me "decrypt" them?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs