AnsweredAssumed Answered

Adding Blocks to the Iteration Cumulative Flow Diagram

Question asked by d33d679938fc80c0203821e17f6a4877 on Nov 13, 2015
We use the Iteration Cumulative Flow Diagram extensively in our organization to "tell the story of what happened" after each iteration.  It is a very effective way to illustrate exactly what happened during the iteration, with one exception -- blocked stories.  This hit me this week when one of my teams had finished a 3-month long project on time with the exception of two stories that were blocked because of external dependencies.  It would have told a better story if the blocked stories had been accounted for.  For example if the graph looked something like this:

0EM14000000MW54
This would probably need to be something configurable because not everyone would want to see it.  However it would be a more accurate depiction of what happened during the iteration.

Thoughts?
ant
 

Outcomes