-
Suggestion
-
Resolution: Answered
-
None
-
None
-
None
Currently the GH burndown chart does not show the stories added or removed after the initial plan. So if a sprint starts with several issues that comprise 16 story points (their committment), and then halfway into the sprint, the team decides to add 1 issue w/4 story points from the backlog, GH will redraw the graph in a way that shows the original committment as 20 story points, which actually the graph should reflect that 4 story points were added 1/2 way into the sprint.
This is misleading because id a team took on more they should get more credit for it or it can be used to help understand "why did our plan change"
Jeff Sutherland showed us how to do this in Scrum (which is also how some google teams do it) by showing a "Change in Committment" line to the story point Burndown chart. The Committement line stays at 0 if there are no changes, but goes down (into negative territory) if story points get added, and goes up if story points are dropped. GH would no longer redraw graphs with the line moving from 16 story points at the beginning to 20 points at the beginning if 4 points were added - rather GH would just draw the graph starting from the 16 points all the way down to -4 points. This keeps the ideal line intact as well as the original committment. See the I attached.
- is related to
-
- Closed
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-373] Add a "Change in Committment" line to story point Burndown chart to show a change in committment (adds/drops)
I already saw a diagram for that kind of thing.
Added story points were added in a negative axis and the red line used both positive and negative axis to show the estimated end of date.
The goal was to show the impact of added task to the estimated end date.
(But the modification of the estimated release date is only interresting for a release burndown chart)
Not sure where I should open this support ticket because I didn't see a greenhopper queue., if there is new process now that you have been bought by Atlassian please let me know.
Virtual Computer has an active support contract with Atlassian and Greenhopper (set to expiration Nov 11, 2009). I have been using the burn down charts for a number of months and had a question. If a story is added midway into the iteration, the point burn down chart does not reflect the change (plus or minus) on that day. Instead it adds the points to the first day of the iteration. For example a 5 point story is added 6 days in, the burn down will not reflect this, it will add the points to the first day of the iteration. I need this to change, a number of iterations we have taken on additional work and it is not recorded anywhere. Having this data will allow us to make better decisions during the iteration, and better planning before it begins. Also I notice the issue burn down does not follow this process - it displays the number of issues at the start then will jump up if issues are added. Again this is a very high priority for us and will dictate our use of Greenhopper moving forward.Thanks
Kevin Amorin
Product Manager
Virtual Computer
From a support ticket
Cheers,
JC
This issue will not be addressed as it is related to Classic boards, which are no longer being improved and will be removed in the future. We encourage you to migrate to the new Agile boards for all future work.
Regards,
GreenHopper Team