Jasper Sonnevelt - Top down or viral spread. What works in your context?

With the success that companies have after trying Kanban, the large scale adoption after a small scale tryout is a hot topic. In this talk two different ways used to implement Kanban in a large organization are discussed. With (bottom up) viral spread in the pilot on one side and top down implementation after that on the other. In this session I will talk about the different approaches used and the effects on the adoption, people and the organization. Both top down and viral spread where used in different phases of the adoption there are both pros and cons to either approach. How these pros and cons manifested in this adoption and how this influenced the succes of the adoption (or lack there of) this organization will be discussed.

Transcript

1. Top Down or Viral Spread? What works best in your context? Lean Agile Scotland 2012
2. About me Jasper Sonnevelt Email: jsonnevelt@vxcompany.com Twitter: @jaspersonnevelt Agile Coach The Netherlands
3. Context • Insurance Company • Around 5000 employees • Internal IT department • Benelux based
4. Pilot • Best people working on too much at the same time • Lot of production defects • Combining of two teams • Scrum didn’t work for these teams
5. • 3 months • 1 team • 2 technologies 11/1/2012 5 Some numbers
7. 11/1/2012 Footer Text 7 And after 3 months… • 7 teams • Quality increased • Happy customers
8. • Start out small • Increased personal responsibility • Increased team member involvement • Multi disciplinary teams • Coaching Pilot success factors
9. “If you want us to help you right now we are happy to do that. We just need the ok of everybody else we are working for right now that we stop working on their stuff”
10. Observations • More confidence • Exploration • Safety to give feedback
11. After the pilot 11/1/2012 Footer Text 11
12. “Kanban is the new standard way of working for development and operations teams”
13. • 19 teams • 200 people participating • 16 facilitators 11/1/2012 13 Some numbers
14. Observations • Some teams doing great • Other teams struggle • At least most teams called it Kanban
15. Results after a year • 9 of the 16 original facilitators quit or are at home with a burn out… 11/1/2012 Footer Text 15
16. Challenges
17. Rapid Expansion
18. End to end collaboration 11/1/2012 Footer Text 18
19. One size fits all
20. My take aways
21. Top down... Footer Text
22. Pros • Having a common language helps • Learning together • Easy to involve stakeholders
23. Cons • Teams might not all feel the sense of urgency • People don’t like being changed • Facilitators were not up to the job
24. Bottom up 11/1/2012 Footer Text 24 • When a lot is in the way • Teams will find their own way
25. Pros • High funfactor • Intrinsic knowledge sharing • Improving faster
26. Cons • Harder to conquer organization • There might not be enough time • Training and coaching
27. Knowledge
28. Complicating factors
29. (Out)Sourcing
30. Next Generation Work • Nothing on the walls • No longer your own desk • Laptops and mobile phones
31. Tooling
32. It takes time
33. Easy does it.. 11/1/2012 Footer Text 33
34. Thank You Email: jsonnevelt@vxcompany.com Twitter: @jaspersonnevelt