Show unexpected activities in burdown charts
|Reported by:||anonymous||Owned by:||hoessler|
it would be nice to tag unexpected activities in the burndown chart, such as changing the content of the current sprint after an emergency meeting.
Some word about motivation/background for this enhancement. If you use the burndown chart as a planing help it has one known weakness. Just from looking at it you can not differentiate if a spike is caused by team updates (to adjust planning to reality) OR if it is caused by an unexpected external event (critical bug needs to be handled). Such events are rare, but they happen more often in the first sprints or when a company is new to agile processes. My suggestion is to tag tickets with unexpected events (after the team decided it can not push them to next sprint) and show them as dots in the burnddown chart.
Here is how it could look like: http://chart.apis.google.com... example image
Hope you like the idea, M