Flow-Based Events in Scrum

Overview

• What you’ll learn: How to integrate flow metrics into Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; using throughput for forecasting; Cumulative Flow Diagrams.
• Prerequisites: Lessons 33–38, plus Module 3 (Scrum Events).
• Estimated reading time: 15 minutes

Introduction

The Kanban Guide for Scrum Teams does not add new events. Instead, it enhances existing Scrum events with flow-based thinking and data. Each Scrum event becomes more effective when informed by flow metrics.

Flow in Sprint Planning

Traditional Sprint Planning often uses velocity (story points completed per Sprint) for capacity planning. Flow-enhanced Sprint Planning uses throughput (number of items completed per Sprint) instead.

Why throughput over velocity? Because throughput is objective (you either finished it or you didn’t), while velocity depends on estimation accuracy (which is notoriously unreliable). With throughput data, you can use Monte Carlo simulations to answer: “Given our throughput range of 6-10 items per Sprint, what is the probability we can finish these 8 items?”

Additionally, review the WIP situation from the previous Sprint. Did items carry over? If so, consider whether your Sprint Backlog was too ambitious or whether blockers caused delays.

Flow in Daily Scrum

We covered the flow-focused Daily Scrum in Lesson 38: walk the board right-to-left, identify aging items, address blockers, and check WIP limits. The key shift is from person-focused (“What did I do?”) to work-focused (“What needs to happen for these items to flow?”).

Flow in Sprint Review

In Sprint Review, share flow metrics with stakeholders. This builds transparency and trust:

• Throughput: “We completed 9 items this Sprint, compared to an average of 8.”
• Cycle Time: “Our average cycle time was 4 days, down from 6 last Sprint.”
• Blocked items: “Two items were blocked for 5 days waiting on API access from the partner team.”

Stakeholders who see data become partners in improvement. Stakeholders who only see demos remain spectators.

Flow in Sprint Retrospective

The retrospective is where flow data becomes improvement action. Use the Cumulative Flow Diagram (CFD) to visualize how work flowed through the Sprint:

• Widening bands in the CFD indicate growing WIP — work is entering a state faster than it is leaving.
• Flat lines indicate no work moved through that state during that period — a bottleneck or idle time.
• Consistent bands indicate healthy, steady flow.

Ask: Where did flow break down? What caused the bottleneck? What one thing can we change to improve flow next Sprint?

The Cumulative Flow Diagram (CFD)

A CFD is a stacked area chart showing the quantity of work items in each state over time. It is the single most powerful visualization tool for flow. Reading a CFD:

• The vertical distance between two bands = WIP in that state.
• The horizontal distance between two bands = approximate cycle time.
• The slope of the top band = throughput (items arriving).
• The slope of the bottom band = throughput (items completing).

Key Takeaways

• Use throughput (not velocity) for Sprint Planning forecasting.
• Focus on work flow, not individual status, in Daily Scrum.
• Share flow metrics with stakeholders in Sprint Review.
• Use CFD and flow data to drive improvements in Retrospective.
• The CFD is the most powerful visualization for flow analysis.