Agile france2013 samuelretiere
•Download as PPTX, PDF•
1 like•3,894 views
This document discusses strategies for widely disseminating the Kanban approach within an organization. It outlines training methods that involve experimentation and continuous improvement, such as using visual tools and games to explain concepts. It also emphasizes spreading Kanban through communities of practice and conferences, and addressing people's expectations by focusing on collaboration over individual competencies. The goal is to help both development and operations teams adopt Agile and Kanban principles by selecting the right approaches and timing based on each group's unique needs and readiness for change.
Report
Share
Agile france2013 samuelretiere
- 1. May, 23rd 2013 Agile France 2013 Comment diffuser massivement une approche Kanban
- 2. 2 Agenda Context People Learn Explain Spread 2
- 3. 3 Pain points driven In Kanban we trustCulture Scrum only Objective 0 5 10 15 20 25 Ops Dev Teams using Kanban Context
- 4. 4 People : Nobody’s perfect but a team can be ITEC COO TUP SGCIB Centre Agile Completer-Finisher Co-ordinator No referent Implementer Monitor Evaluator Plant Shaper The early adopters Jean-Marc DECOULEUR Thierry MONTULE Samuel RETIERE Iconography : Belbin
- 5. 5 People : Expectations You are smart enough Be the best at what we do Jean-Marc DECOULEUR Laurent MORISSEAU David ANDERSON
- 6. 6 Method to learn : I don’t know, Experiment (1/2) Size of the team One team fit all : 1 daily meeting with 21 people • 25 people seems to be the limit to insure collaboration Small teams : Creation of a (light) dedicated pattern • More about practices than coaching Trainings No training : Start with what you do now • Only for senior coach and a good level of trust between IT manager and coach No more slides (Wall of fame) • A visual management approach with posters to get a global picture Short games to explain the theory • Flow ball game, Penny game,… 6 Results
- 7. 7 Method to learn : I don’t know, Experiment (2/2) Daily meetings A pull system • From right to left Only talk about turned cards Dynamic assignation during daily meeting • Reinforce engagement of the team Retrospective Improve fast • The Toyota Kata 7 Results
- 8. 8 Learn : Not always the best 8 Talk about commitmentsStart with limits at the beginning Sometimes start with technical coaching to be able to get a laminar flow
- 9. 9 Learn : Continuous Improvement Purpose Improve Kanban People Kanban practitionners Product Community of practices Process 2 ways of development The Kanban corner Quaterly conference « Agile with Kanban » Digital community Trainee for summerAssistance could have been better Help needed
- 10. 10 Learn : References Conferences Lean Kanban Book club Books Must read Web Blogs Culture Distributed teams Twitter Can’t go outside France Travels Management style is different especially on assignment
- 11. 11 Explain : Spreading rumour (1/2) Scrum vs Kanban « The coach chooses the framework regarding his own competences » Decision chart Only a guideline, not a process Be able to explain your choices
- 12. 12 Explain : Patchwork (2/2) Scrum Facilitation Kanban Software Craftmanship Lean Management Operational Excellence Let’s talk about patchwork Stop trash talking
- 13. 13 Spread : Operations (1/2) WALLOFCONFUSION43% 2% Development I want change Operations I want stability Agile Agile Before Fev 2013
- 14. 14 Spread : Operations (2/2) Kanban for management Ops executive committee Coaching Agile Center Wait for the right momentum Proofs of concept Q&A, Integration, Support After Fev 2013
- 15. 15 Questions
Editor's Notes
- The voice of the sponsor speaking …