Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method. The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban

1. Kanban Basics
Pawel Brodzinski
pawel.brodzinski@gmail.com
http://blog.brodzinski.com

2. What is Kanban?
Kanban is an approach to change
management. It isn’t a software
development or project management
lifecycle or process.
David Anderson

3. Kanban in a nutshell
3rules
1tool
simple mechanics
Visualize workflow
Limit WIP
Measure flow

4. Scrum in a nutshell
Small, cross-functional teams
Product split into small, roughly
estimated, stories
Iterations
Continuous improvement

5. Scrum versus Kanban
Team
KANBANSCRUM

6. Scrum versus Kanban
Iterations
Iteration length [weeks]
0 2 4 8 16 32 64 . . .
KANBAN
SCRUM

7. Scrum versus Kanban
Product management
Product
Backlog
Sprint
Backlog
Shippable
Product
2-4
weeks
1 day
KANBANSCRUM

8. Scrum versus Kanban
Continuous improvement
KANBANSCRUM
Retrospectives

9. Scrum versus Kanban
Board
KANBANSCRUM

10. Why Kanban?
Sometimes time-boxing doesn’t work
Easy integration with other processes
Organizational constraints
Minimal entry barrier

11. How to start with Kanban?
1.
2.

12. Kanban kick start
The most basic board

13. Kanban kick start
Limits

14. Kanban kick start
Backlog

15. Kanban kick start
SDLC

16. Kanban kick start
Transition criteria

17. Kanban kick start
Board summary
Map current process
Start simple
Improve over time

18. Kanban kick start
Tasks: MMF
MMF = Minimal
Marketable Feature
*- if possible…
*

19. Kanban kick start
The board – day 0

20. Kanban kick start
The board – day n

21. Kanban kick start
Dealing with backlog

22. Kanban kick start
Todo queue

23. Kanban kick start
Responsibility for tasks

24. Kanban kick start
Testing

25. Kanban kick start
Blockers

26. Kanban kick start
Blockers

27. Kanban kick start
Priority lane

28. Kanban kick start
Multiple projects

29. Kanban kick start
Multiple projects

30. Kanban kick start
Deployment

31. Kanban kick start
Deployment

32. Kanban kick start
Continuous improvement

33. Kanban kick start
Estimation
WIP
Cycle time

34. Kanban is (only) a tool

35. Kanban
Many of results of Kanban are
counterintuitive. What appears to be
very mechanical approach – limit WIP
and pull work – actually has profound
effects on people and how they interact
with one another.
David Anderson

36. Thank you
Questions?
Pawel Brodzinski
pawel.brodzinski@gmail.com
http://blog.brodzinski.com
http://vsoft.pl
@pawelbrodzinski