Jasper sonnevelt pitfalls of a large kanban implementation
•Download as PPT, PDF•
2 likes•1,113 views
![Pitfalls of a large kanban Implementation Jasper Sonnevelt Email: [email_address] | jsonnevelt@vxcompany.com Twitter: @jaspersonnevelt](https://image.slidesharecdn.com/jaspersonnevelt-pitfallsofalargekanbanimplementation-111113055755-phpapp02/85/Jasper-sonnevelt-pitfalls-of-a-large-kanban-implementation-1-320.jpg)
![Content ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Similar to Jasper sonnevelt pitfalls of a large kanban implementation
Similar to Jasper sonnevelt pitfalls of a large kanban implementation (20)
More from AGILEMinds
More from AGILEMinds (20)
Recently uploaded
Recently uploaded (20)
Jasper sonnevelt pitfalls of a large kanban implementation
- 1. Pitfalls of a large kanban Implementation Jasper Sonnevelt Email: [email_address] | jsonnevelt@vxcompany.com Twitter: @jaspersonnevelt
- 7. Challenges and pitfalls Rapid Expansion Multidisciplinary Teams End-to-End Collaboration (Out)Sourcing Budgets Changing organization Crisis Next Generation Work Culture Management Digital Boards One change at a time Knowledge levels Time Rapid Expansion Multidisciplinary Teams End-to-End Collaboration (Out)Sourcing Budgets Changing organization Crisis Next Generation Work Culture Management Digital Boards One change at a time Knowledge levels Time
- 22. Thank you
Editor's Notes
- Old situation: Technology oriented structure. Technology like Java, .Net, Oracle Technology A works for business line X,Y,Z Technology B works for business line X,Y,Z Technology C works for business line X,Y,Z New Situation: Multidisciplinary teams in a business line oriented structure so Team D consisting of Tech A,B,C works for BL X Team E consisting of Tech A,B,C works for BL Y Team F consisting of Tech A,B,C works for BL Z
- Talk about some challenges
- Opgelegd door management 7 – 20 teams 50 – 200 mensen Relatief korte tijd: March first 10 teams May rest
- Sourcing Not English speaking company Cultural differences Increased uncertainty with employees If I cant see you how will I know that you will build what I asked you to build Distributed Kanban Again something new. You ask a lot of people if in a short period of time you first want them to learn kanban and then apply it to distributed kanban aswel
- - Invest in knowledge Teach and coach Pilot successfactors were: Viral spread doesn’t automaticly work for knowledge and experience
- There is a difference between physical & digital boards Digital: Easily accessible Automatic Metrics Available everywhere Looks cool Works great with distributed teams Physical
- 5 large changes in short amount of time: No more own workplaces Introduction of Kanban Matrix organization New management Increased sourcing Moving locations Multidisciplinary teams
- As much a cultural change as it is a change in the way of working
- 4 teams are still not using a kanban board Too small - Budget for only for 400 hours of work over the whole year Not enough work Not enough priority
- Dave Snowden (keynote LSSC11 Long Beach): Don’t expand unless you know why something is a success. If you don’t know how it works you cant scale it up or down.
- Dynamics: Using digital boards has consequenses. Weigh them Scale consiously: Kanban doesnt fit on every team in the same way