Create a cumulative flow diagram with few a clicks. Test it yourself.
More information, more complexity
When you’re carrying out a project, you are not only interested in its current state. It’s more important to learn where the problems that could endanger the project’s conclusion are, and counteract them. To do that you need facts, data, information. A burndown chart only tells you how much work still needs to be done in the current sprint. A cumulative flow diagram, on the other hand, shows information about how many requirements there are, at which point in time and in which implementation state. And because this information is presented as a bundle, you can better recognize dependencies and possible dangers for the project and plan subsequent projects better – if you know how to interpret the diagram.
The rule is basically: