Kanban is an approach to change management. It isn’t a software development or project management lifecycle or process.
David Anderson
Kanban in a nutshell
3 rules
1 tool
simple mechanics
Visualize workflow
Limit WIP
Measure flow
Scrum in a nutshell
Small, cross-functional teams
Product split into small, roughly estimated, stories
Iterations
Continuous improvement
Scrum versus KanbanTeam
KANBANSCRUM
Scrum versus KanbanIterations
Iteration length [weeks]
0 2 4 8 16 32 64 . . .
KA
NB
AN
SC
RU
M
Scrum versus KanbanProduct management
Product Backlog
Sprint Backlog
Shippable Product
2-4weeks
1 day
KANBANSCRUM
Scrum versus KanbanContinuous improvement
KANBANSCRUMRetrospectives
Scrum versus KanbanBoard
KANBANSCRUM
Why Kanban?
Sometimes time-boxing doesn’t work
Easy integration with other processes
Organizational constraints
Minimal entry barrier
How to start with Kanban?
1.
2.
Kanban kick startThe most basic board
Kanban kick startLimits
Kanban kick startBacklog
Kanban kick startSDLC
Kanban kick startTransition criteria
Kanban kick startBoard summary
Map current process
Start simple
Improve over time
Kanban kick startTasks: MMF
MMF = Minimal Marketable Feature
* - if possible…
*
Kanban kick startThe board – day 0
Kanban kick startThe board – day n
Kanban kick startDealing with backlog
Kanban kick startTodo queue
Kanban kick startResponsibility for tasks
Kanban kick startTesting
Kanban kick startBlockers
Kanban kick startBlockers
Kanban kick startPriority lane
Kanban kick startMultiple projects
Kanban kick startMultiple projects
Kanban kick startDeployment
Kanban kick startDeployment
Kanban kick startContinuous improvement
Kanban kick startEstimation
WIP
Cycle time
Kanban is (only) a tool
Kanban
Many of results of Kanban are counterintuitive. What appears to be very mechanical approach – limit WIPand pull work – actually has profound effects on people and how they interact with one another.