When we hear about project management methodology we usually think of structured, standardized set of rules, that tells us how should we organize the project team and its work. This is true in both, formal methodologies and those related to Agile. As a result, the implementation of new methodology often means a big change for the team or the company. It is one the reasons why those implementations fail in many cases. Why is Kanban different? It doesn't try to immediately change the way the project team works. It doesn't impose certain team organization, specific techniques or artifacts. It is flexible and easily changes to fit different situations. And in the same time, despite its simplicity, it helps to define and correct the problems that jeopardize the project. This presentation shows how Kanban functions in practice and points out in what areas can it be use: from organizing your own tasks to managing products portfolio.

1. Kanban
Light-weight alternative
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski

2. About me
VSoft
Software Project
Management
http://blog.brodzinski.com
Project Management
Stack Exchange
http://pm.stackexchange.com/

3. Once upon a time, in a galaxy far, far away,
on some fine event…

4. Agile is all about shrinking
the feedback loops.
Corey Haines

5. Feedback loops
Formal Agile
methods methods

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

8. Few rules, 1 tool, simple mechanics

9. Kanban
Visualize workflow
Limit WIP (Work In Progress)
Measure Flow
Make policies explicit
Improve

10. KANBAN
BOARD

14. Limits

15. MMF, User Story, Work Item…

16. CYCLE TIME
LEAD TIME

17. IMPLEMENTATION

18. Kanban implementation is fast
and simple…

19. …except it changes nothing…

20. …at least at the very beginning

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

23. POSSIBLE
APPLICATIONS

24. Manufacturing

25. Maintenance projects

26. Software development

27. Project portfolio management

28. Personal Kanban

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

31. 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

32. Questions?
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski