Learn how Kanban's flow practices strengthen the Scrum framework rather than replacing it. Visualise the Sprint Backlog as a Kanban board, add WIP limits and read flow metrics to improve within-Sprint visibility and predictability — without touching a single Scrum accountability or event.
Watch the free preview
The within-Sprint visibility problem — free to watch, no account needed.
What you'll learn
- Explain how Kanban complements the Scrum framework without replacing any accountability, event or artifact
- Describe the four flow metrics — WIP, cycle time, work item age and throughput — and what each one reveals
- Apply WIP limits to an existing Sprint Backlog board to make bottlenecks visible
- Diagnose an overloaded Scrum board and redesign its flow using WIP limits and a Definition of Workflow
- Produce a Scrum + Kanban board configuration guide your team can adopt in one Sprint
Syllabus
Why Scrum Teams Need Flow
The within-Sprint visibility problemFree preview
Kanban complements Scrum, it does not replace it
The Flow Toolkit
The four Kanban practices and the Definition of Workflow
Flow metrics and WIP limits
Putting Flow to Work in a Sprint
Turning the Sprint Backlog into a flow board
Case study — fifteen items in progress for five people
Making Flow Stick
Your Scrum + Kanban board configuration guide
Common traps and anti-patterns to avoid