the other side of Kanban - #lkuk13

Presented at Lean Kanban UK 2013

When we talk about Kanban we often focus on how the increased attention to flow can benefit our organisations and customers economically. We talk about the improvements it can bring by helping us reduce lead times, manage risk, discuss cost of delay etc.

Creating a culture of continuous improvement is also at the heart of the Kanban method but again we often target the economic benefits when we strive to identify and remove waste, increase predictability and produce higher quality software.

But what does Kanban mean for the individuals who work inside the system?

In this session we'll explore how the Kanban principles and practices can foster understanding, belonging and purpose in the workplace.

Transcript

1. Chris McDermott @chrisvmcd the other side of Kanban Wednesday, 30 October 13
2. Wednesday, 30 October 13
3. Wednesday, 30 October 13
4. Wednesday, 30 October 13
5. respect for people Wednesday, 30 October 13
6. people come to work each day to do a good job respect for people Wednesday, 30 October 13
7. people come to work each day to do a good job respect for people appreciation of a system Wednesday, 30 October 13
8. people come to work each day to do a good job respect for people appreciation of a system neglected the innovative capabilities Wednesday, 30 October 13
9. people come to work each day to do a good job respect for people appreciation of a system neglected the innovative capabilities attend to their needs Wednesday, 30 October 13
10. “attend to folks’ needs” #AntimatterPrinciple Bob Marshall aka @flowchainsensei Wednesday, 30 October 13
11. The Kanban Method Wednesday, 30 October 13
12. inclusive Wednesday, 30 October 13
13. start with what you do now agree to purse incremental and evolutionary change initially, respect current roles, responsibilities & job titles encourage acts of leadership at all levels Wednesday, 30 October 13
14. Wednesday, 30 October 13
15. shared understanding Wednesday, 30 October 13
16. Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** HT @Caza_no7 Wednesday, 30 October 13
17. Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Wednesday, 30 October 13
18. Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Wednesday, 30 October 13
19. Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** HT @Caza_no7 Wednesday, 30 October 13
20. Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** HT @Caza_no7 Wednesday, 30 October 13
21. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Wednesday, 30 October 13
22. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
23. Wednesday, 30 October 13
24. intrinsic motivation Wednesday, 30 October 13
25. autonomy Wednesday, 30 October 13
26. Wednesday, 30 October 13
27. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
28. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
29. Wednesday, 30 October 13
30. mastery Wednesday, 30 October 13
31. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
32. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
33. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Exit criteria: • Code clean & checked in • Integrated & tested • Running on a UAT env Wednesday, 30 October 13
34. Wednesday, 30 October 13
35. (shared) purpose Wednesday, 30 October 13
36. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Done Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested • Running on a UAT env Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
37. Wednesday, 30 October 13
38. belonging Wednesday, 30 October 13
39. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Ready to celebrate Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested • Running on a UAT env Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest HT @agilesensei Wednesday, 30 October 13
40. Wednesday, 30 October 13
41. flow Wednesday, 30 October 13
42. Story title **/**/2011 214*** Demand (4) Analysis (5) Dev (6) Test Released In Progress Done In Progress Done In Progress (2) Ready to celebrate Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Exit criteria: • Goal is clear • First Storys defined Exit criteria: • Code clean & checked in • Integrated & tested • Running on a UAT env Exit criteria: • Customer accepted • Ready for production Pull Criteria: 1) Expedite 2) Fixed Date in danger 3) Oldest Wednesday, 30 October 13
43. happiness Wednesday, 30 October 13
44. 1- the pleasant life happiness Wednesday, 30 October 13
45. 1- the pleasant life happiness 3 - the meaningful life Wednesday, 30 October 13
46. 1- the pleasant life happiness 3 - the meaningful life 2 - the good life Wednesday, 30 October 13
47. Wednesday, 30 October 13
48. safety Wednesday, 30 October 13
49. C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
50. C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
51. C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
52. C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
53. What should I do next? C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
54. We get no time to think! What should I do next? C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
55. We get no time to think! What should I do next? This is thankless work! C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
56. We get no time to think! What should I do next? This is thankless work! I am stressed C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
57. We get no time to think! What should I do next? This is thankless work! I am stressed Why don’t they just follow the process! C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
58. We get no time to think! Another late night! What should I do next? This is thankless work! I am stressed Why don’t they just follow the process! C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
59. We get no time to think! Another late night! What should I do next? This is thankless work! I am stressed Why don’t they just follow the process! @$%£!! C all C entre Sales F in an ce Developm ent Wednesday, 30 October 13
60. Next (5) Doing (5) Done Priorities High Low Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Call Centre Sales Finance Dev Ops Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** HT @Caza_no7 Wednesday, 30 October 13
61. Next (5) Doing (5) Done Priorities High Low Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Call Centre Sales Finance Dev Ops Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** **/**/2011 Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** Story title **/**/2011 214*** HT @Caza_no7 Wednesday, 30 October 13
62. Wednesday, 30 October 13
63. thank you! http://speakerdeck.com/chrisvmcd Books www.amazon.co.uk/Future-Management-Gary-Hamel/dp/1422102505 www.amazon.co.uk/New-Economics-Industry-Government-Education/dp/0262541165 www.danpink.com/books/drive Blogs flowchainsensei.wordpress.com/2013/10/12/the-antimatter-principle www.djaa.com/what-business-are-you www.software-kanban.de/2012/07/what-f-is-pull.html itopskanban.wordpress.com Pictures www.islandofkevinmoreau.com/on-regret blogs.kqed.org/bayareabites/2012/08/13/outside-lands-2012-photos-food-art-music-people blog.doostang.com/2009/11/10/how-to-break-into-a-career-on-wall-street-what-your-professors-dint-or-couldnt-tell-you Wednesday, 30 October 13