Editor’s note: This blog post was originally published in October 2018 and has been completely revamped and updated for accuracy and comprehensiveness.
Agile comes in many different flavours, and our goal with ZenHub has always been to provide teams with a way to work closer to the code regardless of what methodology they’ve adopted.
That’s why today we’re excited to announce the first, of many, coming features aimed at making it even easier for Kanban based teams to track progress using ZenHub: Cumulative Flow Diagrams.
What is a Cumulative Flow Diagram, Anyway?
Cumulative Flow Diagrams provide teams with critical insights into how different areas of their workflow are changing over time. With Cumulative Flow Diagrams, teams have the ability to:
- Understand the throughput of Issues through pipelines on the Board
- Identify bottlenecks and areas where Issues are piling up in pipelines
- Proactively make process improvements to streamline development
Unlike ZenHub’s Burndown, Velocity, and Release reports, Cumulative Flow Diagrams aren’t based on Estimates (Story Points). For this reason, they’re a great way for non-Scrum based teams to visualize and understand how Issues are progressing through the Board.
Visualize the Throughput of Issues on the Board
Each coloured area of the report represents a different pipeline or workflow stage within your workspace, with the vertical height of each area representing the total number of issues within that pipeline at a point in time. As new work is initiated, and Issues are added to the Board, the Diagram makes it possible to visualize how those Issues are moving through the different stages of the workflow.
The diagram gives teams the ability to track the throughput of Issues over the past 14 days, 30 days, 3 months 6 months or a custom date range within the last 6 months.
Identify Bottlenecks and Unblock the Team
By visualizing the number of Issues within a pipeline, Cumulative Flow Diagrams make it easy for teams to identify bottlenecks where work is piling up. For example, if the volume of Issues within your team’s
Review pipeline is continually growing, this might serve as an indicator that more team members need to get involved in reviewing Issues and Pull Requests.
Check out sample cumulative flow diagrams we've put together to help your team identify different trends that may occur.
Make Workflow Changes to Improve Your Process
Beyond identifying bottlenecks, Cumulative Flow Diagrams can also provide indications as to where the team might benefit from workflow changes and process improvements. For example, if your team is continually finding that your
In Progress column is growing while your
Review pipeline remains flat, that could indicate the need to implement work in progress (WIP) limits.
While these process changes will differ from team-to-team, Cumulative Flow Diagrams make it possible for teams to have proactive conversations and take action before important projects and deadlines are put at risk. In the true spirit of Agile, it’s these insights that facilitate the ability for continuous learning and improvements in the way teams deliver software projects.
Ready to get started with Cumulative Flow Reports? Visit the Reports section of ZenHub and select ‘Cumulative Flow’ to start visualizing your workflow. For more information on how your team can make the most of this new report, check out our help centre.