@reiver

Kanban versus Scrum

[In Kanban,] Doing > Talking

[...]

Scrum

  • Estimation
  • Talking / Planning
  • WIP is uneven across roles
  • Squeeze on QA
  • Squeeze on PO
  • No downtime
  • Big Backlogs

[...]

Kanban

  • No time-boxes [that you find in Scrum]
  • No estimation
  • Cycle Time replaces Velocity [used in Scrum]
  • Slacktime
  • Visualize work
  • Limit work in progress (WIP)
  • Measure and manage Flow

[...]

[With Kanban] Measure

  • Time to complete a cycle
  • Throughput
  • Value delivered
  • Quality
  • Developer days per completed item

[...]

Kanban #recap

  • Visualize a process
  • Limit work in process (WIP) to improve throughput and cycle time
  • Measure and manage Flow to handle bottlenecks
  • No time-boxes
  • No estimation
  • Cycle Time replaces Velocity
  • Idleness is not a bad thing

Takeaway

  • Visualization
  • Measurement
  • Continuous improvement (experimentation)

-- Noel Pullen

from "Kanban: July 17, 2012 @ UBC"

Quoted on Sun Jul 29th, 2012