Manuals / Agile & Scrum / Chapter 5

B · Practice · intermediate · ~35 min · Chapter 5 of 10

Kanban: flow over sprints

Visualize work, limit WIP, manage flow, make policies explicit. Use when interrupt-driven work or continuous delivery fits better than fixed sprints.

Path progress
45%

Step 1 of 2

Map the workflow

Columns should match reality (Ready → In progress → Review → Done), not aspirational theater.

Map the workflowDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Map the workflowdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Draw a board with WIP limits on In progress and Review. Justify each limit in one line.

Was this step clear?
Chapter learning outcomes
  • WIP limits
  • Cycle time
  • Classes of service
  • Scrum + Kanban hybrids

Clear these before you leave