Skip to content

Cumulative flow diagram

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

  • This would be similar to a burndown chart in that it would be used by a team within a single milestone to see how their issues are being completed.
  • It is more advanced than a burndown chart since you get more information.
  • Mechanically, it it stacked chart. (So imagine stacked colors in the mockup below.) And it is fully integrated into a board.
  • Suppose you have already scoped your board to milestone 11.5. Suppose in your board, you have workflow stages (represented as lists), with Open, In dev, In review, In QA, Closed.
  • The chart is a stacked chart with those lines. So Closed is the last stage, so it is at the bottom. And then you have In QA stacked on top of that, and then In review, and then In dev.
  • All issues represents all issues in that milestone. (So in the mockup below, you see that the scope increased in the middle of the milestone, since All issues went up.) Note that All issues is not stacked above the other lines. This is how a cumulative diagram works. So the design should somehow make that clear.
  • We would have a version for both issue count and issue weight.
  • This is a great article on why this visualization is very powerful, and we can add additional helper UI elements to illustrate it. (I.e. show horizontal / vertical gaps between lines.)

A user permitted me to share that they are already creating something similarly themselves. This is what it looks like

*This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.*
Edited by 🤖 GitLab Bot 🤖