# Feature AGILE-12 - Cumulative flow diagram

Project: Stream agile
Status: specified
URL: https://community.openproject.org/work_packages/AGILE-12

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | RM Agile, Agile Reporting |
| Roadmap | 2027 Q3 |
| Relevance | Medium — Useful Mid-Term |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Enterprise / Professional (PRO) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/owpxg3fdqZONIGL6SBSG8M/Agile--Sprint-reports?node-id=1544-39300&t=vw9kH6nwC2lYoUGl-0 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Rosanna Sibora |
| Feature Lead |  |
| Developers | OP Dev Polaris Team |
| Designer | Julia Racsko |
| Ordered by |  |
| Signed off by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work | 30d 0h |
| Labor costs |  |

## Description

### Story

In order to **track the work in progress**,  let's **add a cumulative flow diagram**.

### Explanation

We work on work packages, some need to be tested, some need to be specified, some need to be developed, some need to be fixed. It's not easy to know where to put efforts.

Being able to view the flow of work would help me decide what to work on next.

I think a Cumulative Flow Diagram can help visualize it. It looks like this:

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg?w=870" alt="0" srcset="https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg 292w, https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg?w=150 150w" sizes="100vw"></div></figure>

In a workflow, it tracks the status of work packages over time in a cumulative graph.

Reading distance vertically gives an idea of the work in progress: how many work packages are in a particular status at the moment?

Reading distance horizontally gives an idea of the cycle time: how much time does it take on average for a work package to transition from one status to another?

Some patterns can also exhibit problems: if test line is growing faster than done line, that can means there are not enough efforts put in testing, and developing more is counter productive. If dev line is growing faster than test, that can mean there is a lot of unfinished work or maybe some people are stuck. And so on.

You can read more on <https://getnave.com/blog/how-to-read-the-cumulative-flow-diagram-infographic/>

You can learn even more on <http://brodzinski.com/2013/07/cumulative-flow-diagram.html> (from 2013)

It can also give good insights for retrospective discussions.

### Acceptance criteria

There may be multiple ways to address this story. Here is a proposition:

  - a CFD widget is part of the sprint report page
    
      - The widget is a stacked line chart (curved ideally) with three data series (groups of statuses) any work package associated to the sprint has had or has
        
          - The unit selected for the project (<mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">\#\#\#AGILE-198</mention>) determines whether story points, work or number of work packages is used.
            
              - \[open\] double check with <mention class="mention" data-id="99542" data-type="user" data-text="@Rosanna Sibora">@Rosanna Sibora</mention>
        
          - The three data series are work packages grouped by status:
            
              - created: having the default meta-status
                
                  - \[open\] check if the default meta-status is being removed. If so, check for what replaces it.
            
              - in progress: having neither the default nor the closed meta-status
            
              - resolved: having any of the closed statuses configured for the project in the backlogs settings.
        
          - All data series should always be present. E.g. even if no work packages was resolved, the series for it should be shown.
        
          - The data series end:
            
              - if the sprint is completed: at the point in time the complete button was pressed
            
              - if the sprint has started: at the current point in time
        
          - The resolution of the values is hours.
            
              - The time is the local time of the user.
    
      - Non working days are shown as days with a gray background.

  - Follows <mention class="mention" data-id="78631" data-type="work_package" data-text="###AGILE-399" data-display-id="AGILE-399">\#\#\#AGILE-399</mention>specification on the start end end date

  - Uses the same blankslates as specified in <mention class="mention" data-id="76439" data-type="work_package" data-text="###AGILE-308" data-display-id="AGILE-308">\#\#\#AGILE-308</mention>

**Out of scope for now (will be implemented in further iterations):**

  - A project and some work package types can be selected

  - The time span is configurable

  - CFD view can be bookmarked and shared

  - Statuses can be selected too, and categorized together in one category (for instance new, specified, needs clarification can all be grouped in a "backlog" category)

  - Rendering a projection line
