Many people still treat Kanban as project management or software development method, which it isn't. However even for those who consider Kanban as change management framework the mechanics of improvements fostered by Kanban remains somewhat vague. The nature of the method which often results in improvements introduced subconsciously doesn't really help. When we think about Kanban improvements we usually expect simple dependencies, e.g. we introduce visualization so everyone knows better what the current status of the project is. At the same time many changes incepted by Kanban are hardly predictable, which is a reason why the method is sometimes undervalued and dubbed as a simple workflow approach. The session will discuss a real-life example of a chain of changes in team behavior after introducing Kanban. Connections between each step will be drawn to show how people and teamwork has changed and how it was all started with introducing a very simple tool - Kanban. After the presentation the audience should learn how much improvement potential can be introduced and how many different areas are affected by Kanban adoption.

1. Surprising truth about
Kanban improvements
Pawel Brodzinski
@pawelbrodzinski
#abe2011

2. Hi, I’m Pawel
VSoft
http://vsoft.pl
Software Project
Management
http://blog.brodzinski.com
Project Management
Stack Exchange
http://pm.stackexchange.com/
Twitter
@pawelbrodzinski

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

7. 2 3 2 1

8. 2 3 2 1

11. Examples:
http://vimeo.com/22431607
http://www.slideshare.net/pawelbrodzinski/kanban-improvements-
emergent-behavior

13. :

14. 2 3 2 1

15. 2 3 2 1

16. 2 3 2 1

17. 2 3 2 1

19. !

21. !

23. !

25. !

30. Thank you
Questions?
Pawel Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski