2. Scrum is easy!
• You just have to:
prioritize a month ahead
estimate
commit to just enough work
develop and test within the sprint
fend off interruptions
get DONE with everything
repeat without fail month after month
tor@hovland.name
3. If you can do this, keep doing it!
tor@hovland.name
4. Kanban may be better
• No sprints
• Just a continuous flow of work
tor@hovland.name
5. Particularly well suited
• when it is hard to make a backlog
up-front
support projects
innovative projects
tor@hovland.name
6. Limited work in progress
• Just as a currency note is a valuable
share of limited money ...
• ... a Kanban is a valuable share of
limited work capacity.
• A task with a Kanban is privileged,
because it will get done quickly.
tor@hovland.name
7. No need to choose. Adapt step by step.
• Perhaps you end up doing
50% Scrum, 50% Kanban.
tor@hovland.name
8. From Scrum to Kanban in 10 easy steps!
tor@hovland.name
9. Step 1: The Scrum board • Everything is in progress :-o
tor@hovland.name
10. End of sprint • Nothing is finished :-O
tor@hovland.name
17. Step 8: Drop the iterations
• The purpose of the iterations are
close to zero now and can be
dropped.
• But if you like to have sprint goals
and timeboxes, you can keep them.
tor@hovland.name
19. Step 10: Optimize WIP limits
• Don’t increase a limit when the problem is
work piling up somewhere else.
tor@hovland.name
20. Even if you don’t want to drop Scrum
• Try limiting WIP
• ... by not starting a user story until
you absolutely have to.
• Better to really finish 2 stories
• ... than to finish 3 in a hurry and
having to rework them later.
tor@hovland.name
21. More info
• Corey Ladas’s book
• Kniberg & Skarin’s
”Kanban and Scrum”
• tor@hovland.name
tor@hovland.name
