Flow Metrics Report (Scaled Agile Framework, SAFe)

Owned by Rustem Shiriiazdanov
Nov 27, 2024
3 min read

This SAFe (Scaled Agile Framework) report script is a comprehensive analysis and visualization tool designed to provide insights into sprint progress, cumulative flow, cycle time, and system throughput.

Purpose

This report aims to

  • Provide a clear overview of sprint progress and team velocity.

  • Highlight bottlenecks or inefficiencies in the workflow by analyzing cycle time and cumulative flow.

  • Enable actionable insights through drill-down capabilities and detailed status history tracking.

Use Cases

  • Agile Coaches: To assess team performance and identify areas for process improvement.

  • Scrum Masters: For tracking sprint health and ensuring alignment with sprint goals.

  • Product Owners: To monitor issue progress and delivery timelines.

 

Report Functionality

Report Overview:

image-20241127-104142.png


Chart contains following visualisations:

  • Cumulative Flow Diagram (CFD): Displays issue statuses over time, with an overlay of velocity data.

  • Cycle Time Breakdown: Visualizes how much time issues spend in each status over time.

  • System Throughput: Illustrates output rates for each status and the overall system velocity.

  • Charts include interactive elements like tooltips, zoom, and sprint mark areas.

Cumulative Flow Diagram

image-20241127-103444.png
Cumulative Flow diagram with velocity chart

 

Cycle Time Breakdown chart

image-20241127-103556.png
Cycle Time Breakdown diagram with velocity chart

System Throughput chart

image-20241127-103759.png
System Throughput chart with Flow steps throughputs and velocity

 

User guide

1. Sprint Picker

Use the Sprint Picker to define the scope of your report:

  • Project Selection:

    • Select the relevant project (e.g., Mobile Dev (MOBL)).

  • Board Selection:

    • Choose the Scrum board associated with the project (e.g., MOBL Cowboys).

  • Sprints Selection:

    • Pick one or more sprints for analysis (e.g., MOBL Sprint 1, MOBL Sprint 2).

2. Select Issue Types

Filter the report to include only the issue types you are interested in:

  • Examples: Bug, Story.

  • Use this to focus on specific work items relevant to your analysis.

3. Statuses Order

Define the workflow statuses and their order for the report:

  • Examples: To Do, Architecture Review, In Progress, Testing, Accepted, Done.

  • The statuses will appear in this sequence in visualizations like the Cumulative Flow Diagram and Cycle Time Breakdown.

4. First Status

Set the First Status to specify the initial status of issues included in the report:

  • Example: To Do.

  • This is the starting point of the workflow.

5. Last Status

Choose the Last Status to indicate the final status that marks issue completion:

  • Example: Done.

  • This is typically the end of the workflow.

6. Wait Statuses

Define any statuses that represent waiting or inactive periods in the workflow:

  • Examples: To Do, Architecture Review.

  • Note: Currently is no in use in the report

7. Velocity Aggregation

Choose how velocity data should be aggregated:

  • Options include Daily, Weekly, Monthly, or Per Sprint.

  • Example: Daily aggregation will calculate how much work is completed each day.

8. Cycle Time Aggregation

Define the granularity for cycle time analysis:

  • Options include Daily, Weekly, Monthly, or Per Sprint.

  • Example: Daily aggregation will break down the time spent in each status day by day.

Report import

 

Report is not available in public repository yet, but you can import it manually by opening the file below and following this instruction Report Builder: "How to export and import a Scripted Report" guide | Report Import