Skip to content

πŸ“‹ Kanban & Flow Management ​

Continuous flow approach to managing work without fixed iterations.

Core principles ​

  1. Visualize the workflow β€” Board with columns representing stages
  2. Limit Work in Progress (WIP) β€” Cap items per column to avoid bottlenecks
  3. Manage flow β€” Optimize for throughput and lead time
  4. Make policies explicit β€” Define entry/exit criteria for each column
  5. Improve collaboratively β€” Use data to drive process changes

Typical board layout ​

Backlog β†’ Ready β†’ In Progress β†’ Review β†’ Done

Key metrics ​

MetricDefinitionGoal
Lead timeTime from request to deliveryMinimize
Cycle timeTime from start to deliveryMinimize
ThroughputItems completed per time periodStabilize
WIPItems currently in progressLimit

WIP limits ​

  • Set WIP limits per column AND per person
  • If a column is at its limit, help finish existing work before starting new
  • WIP limits expose bottlenecks β€” that's the point

When to use Kanban over Scrum ​

  • Continuous flow of work (support, ops, maintenance)
  • No need for fixed-length iterations
  • Team handles unpredictable incoming requests
  • Work items vary significantly in size

Pergame Knowledge Base