Sustainable development of an organization -- LKFR14
•
0 likes•94 views
The document discusses sustainable development of organizations through lean Kanban principles. It advocates for aligning an organization's communication structure with the structure of its systems to facilitate collaboration. Several techniques are proposed to improve synchronization across teams, including weekly status meetings, retrospectives, and emphasis on simple metrics focused on bugs and cycle time. The overall goal is to evolve practices incrementally over time through experience.
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (20)
Similar to Sustainable development of an organization -- LKFR14
Similar to Sustainable development of an organization -- LKFR14 (20)
Recently uploaded
Recently uploaded (20)
Sustainable development of an organization -- LKFR14
- 1. Sustainable development (of an organization) Lean Kanban France 2014 Pascal Rieux
- 2. Conway’s law: “Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure” http://www.melconway.com/Home/Conways_Law.html
- 3. Structure?
- 6. Before
- 8. Product Stuff Before Roadmap Stuff 1 2 3 5 8 13 20
- 11. Product Sprint Team / Sprint Stuff Before Roadmap Team / Sprint Team / Sprint Stuff
- 15. … After
- 17. Synchronize?
- 19. Every Monday morning 5 min. per topic: demo or status
- 20. Every Monday morning 5 min. per topic: demo or status 5 min. for roadmap update
- 21. Every Monday morning 5 min. per topic: demo or status 5 min. for roadmap update 5 min. for deployment status
- 22. Weekly synchro meeting: 1 hour
- 23. Weekly synchro meeting: 1 hour Ad-hoc meetings
- 24. Weekly synchro meeting: 1 hour Ad-hoc meetings Quaterly retrospectives
- 25. Weekly synchro meeting: 1 hour Ad-hoc meetings Quaterly retrospectives Make-it! day
- 26. Weekly synchro meeting: 1 hour Ad-hoc meetings Quaterly retrospectives Make-it! day Special events
- 27. Objectives?
- 29. Manage hidden topics Minimize time to production
- 30. Manage hidden topics Minimize time to production Evolutive architecture
- 31. Manage hidden topics Minimize time to production Evolutive architecture Extended team & self-organization
- 32. Manage hidden topics Minimize time to production Evolutive architecture Extended team & self-organization Wide-angle visibility
- 33. Manage hidden topics Minimize time to production Evolutive architecture Extended team & self-organization Wide-angle visibility Everyone can lead
- 34. How?
- 35. With time!
- 36. With time Starting where we were
- 37. With time Starting where we were Support from management
- 38. With time Starting where we were Support from management Collaboration with product marketing
- 39. With time Starting where we were Support from management Collaboration with product marketing Evolving incrementally
- 40. With time Starting where we were Support from management Collaboration with product marketing Evolving incrementally People, practices, tools and metrics
- 41. A toolbox?
- 42. Distributed Version Control System
- 43. Distributed Version Control System Automated tests (but not only)
- 44. Distributed Version Control System Automated tests (but not only) Review by pull requests
- 45. Distributed Version Control System Automated tests (but not only) Review by pull requests Containerization of components
- 46. Distributed Version Control System Automated tests (but not only) Review by pull requests Containerization of components Continuous integration
- 47. Metrics?
- 48. Keep Indicators Simple Stupid ;-)
- 49. Keep Indicators Simple Stupid Focus on bugs
- 50. Keep Indicators Simple Stupid Focus on bugs => Count over time
- 51. Keep Indicators Simple Stupid Focus on bugs => Count over time => Cycle time over time
- 52. Keep Indicators Simple Stupid Focus on bugs => Count over time => Cycle time over time Available in real time
- 53. What’s next?
- 55. Micro-service architecture? Testing (xDD + mindset)
- 56. Micro-service architecture? Testing (xDD + mindset) Automation everywhere
- 57. Micro-service architecture? Testing (xDD + mindset) Automation everywhere Individuals and interactions
- 58. Jean-François Jagodzinski : “Une équipe se cultive comme un jardin”
- 59. Questions
- 60. Thank you! pascalrieux64@gmail.com Credits: « Garabit ». Sous licence Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons « Open Make Up For Ever 2013 - Team - France - 14 » par Pierre-Yves Beaudouin — Travail personnel. Sous licence Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons « Edinburgh Munster rugby » par Edinburgh Blog — Action at Edinburgh vs Munster Magners League match at Murrayfield. Sous licence Creative Commons Attribution 2.0 via Wikimedia Commons « Escalade à Milhac » par Jean Roussie — Travail personnel. Sous licence Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons « Felibree-Piegut outils-charpentier 01 » par Traumrune — Travail personnel. Sous licence Creative Commons Attribution-Share Alike 3.0 via Wikimedia Commons « Diamond DA20-C1 C-GEQA Tableau de bord » par Louis Rousseau — Travail personnel. Sous licence Creative Commons Attribution 3.0 via Wikimedia Commons « An artist's impression of a Pioneer spacecraft on its way to interstellar space » by NASA Ames - http://www.nasa.gov/centers/ames/news/2013/pioneer11-40-years.html. Licensed under Public domain via Wikimedia Commons
- 61. Backup
- 62. One key store to bind them all kukume etcd sjt
- 64. After