I've read and seen the arguments for and against tracking story points within a sprint vs hours. However, there are many Scrum professionals out there (myself included) that disagree with tracking hours at all using Scrum. Doing so begs the question from the team and stakeholders of how many hours equal a story point. The Scrum Guide does not tell you to use hours to estimate tasks within a Sprint so it seems strange for Atlassian to take this strong stand. My take is that Story Points are used for planning outside the sprint or for more longer term planning (release planning). Within the sprint though, there needs to be some other measure of progress.
The purpose of using a Sprint Burndown chart is to provide the team with a daily picture of the team's progress so that they can adjust accordingly to meet their sprint goals. Using story points only has the "cliffhanger" effect in that stories can take several days to make it through all development and testing activities. What you get in those cases is a straight line with sharp drop offs mid way through sprints to show the story being completed. This is not effectively helping the team track their progress daily.
We looked for a way to do this in Jira other than using hours for the reasons mentioned above. We noticed recently that you can change the Sprint Burndown chart to reflect when issues count is decremented. This seemed like a good solution, while still somewhat inaccurate as all issues would be weighted equally. We tried this but soon discovered that when Jira says "Issue Count," they do not treat all issue types equally. Specifically, sub-tasks are worthless. The issue count burndown only looks at issues of type Story/Task or higher and ignores sub-tasks. This makes using issue count worthless.
I put this out to the community to see if anyone else has found a way around this issue? We are open to using any alternative measure of tasks inside a sprint other than hours. We want all issue types to show progress on the burndown so that our teams can see overall progress more accurately on a daily basis.
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