Situation: Our sprint review is held at the end of the final sprint day. At the sprint review, the Product Owner would take any incomplete stories and move them to the Product Backlog for prioiritization for the following sprint.
Result: The Sprint burndown chart shows that all issues are complete and remaining work is zero. Therefore, it looks like the team has completed all of the stories and tasks as scheduled. We would prefer to have an accurate represenation of the status on the final day. But, the PO also wants to be pro-active in managing the issues for the next sprint.
Question: Is there a way to update/modify the burndown chart to accurately reflect the status on the final day after the sprint is closed?
That is, modify the data so the graph shows the situation as of the final day at 4PM?
The way I'd recommend is to use GreenHopper's release function on the planning board. This will open a dialog, showing incomplete stories at that point. You can decide where to move them (in your case, into your backlog). GreenHopper will then record the information on the moved issues that they've been part of the sprint you've just released, and the burndown charts in the released board will reflect this.
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