Scaling approaches comparison - Lean/Agile US 2017
•
4 gostaram•4,129 visualizações
The document compares different approaches for scaling agile, including SAFe (Scaled Agile Framework), LeSS (Large Scale Scrum), and program/portfolio Kanban. It notes that most experts agree teams should only scale when they cannot effectively divide work. When dependencies exist between teams, options include SAFe, LeSS, or using a program/portfolio Kanban approach to visualize work. The document asks questions to help determine the best scaling approach based on factors like guidance needed, agility required, and leadership commitment to change.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Scaling approaches comparison - Lean/Agile US 2017
Semelhante a Scaling approaches comparison - Lean/Agile US 2017 (20)
Mais de Yuval Yeret
Mais de Yuval Yeret (20)
Último
Último (20)
Scaling approaches comparison - Lean/Agile US 2017
- 1. Comparison of approaches for Scaling Agile – Yuval Yeret – Lean/Agile US – February 2017, Fort Lauderdale, FL <10 10-30 30-100 >100
- 4. Most experts agree - Scale only when you cannot effectively Divide & Conquer
- 6. The Alternatives New in 2015 We implement The Scaled Agile Framework (SAFe) or something very similar We watched the Spotify movies and used that as inspiration We read Larman&Vodde and are doing LeSS – Large Scale Scrum We are using a Program/Portfolio Kanban to visualize, manage & improve
- 7. Market Share
- 10. Large Scale Scrum - LeSS
- 11. LeSS != EASY
- 12. What do you do when you DO have dependencies between teams?
- 13. Scrum Alliance & LeSS sitting in a tree?
- 16. Synchronizes with PI Planning ! All stakeholders face-to-face (but typically multiple locations) ! Management sets the mission, with minimum possible constraints ! Requirements and design emerge ! Important stakeholder decisions are accelerated ! Teams create—and take responsibility for—plans Future product development tasks can’t be pre-determined. Distribute planning and control to those who can understand and react to the end results. — Michael Kennedy, Product Development for the Lean Enterprise For a short video PI planning example, see: https://youtu.be/ZZAtl7nAB1M
- 19. Make sure the approach you choose gives you face time to discuss Lean/Agile principles and practices with Leaders LEADERSHIP Respectfor peopleandculture Flow Innovation Relentless improvement VALUE
- 21. How do the different Scaling frameworks address where the market is?
- 23. “Help me choose the right scaling approach for my organization”
- 24. Do you even NEED to scale (or can you figure out a way to deliver what the business needs using small autonomous agile teams)?
- 25. How much GUIDANCE are you looking for? How prescriptive do you expect the framework to be? A la carte? Fixed menu?
- 26. How agile do you need to be? How agile CAN you be? e.g. Are we talking Continuous Delivery combined with a really agile-friendly business?
- 27. What level of commitment to change do you have from the organization’s leaders?
- 28. What’s your preference at the team level? Scrum / Kanban / ScrumBan
- 30. What’s Next – in Lean/Agile US Conference and Beyond… yuval@agilesparks.com @yuvalyeret http://www.agilesparks.com/blog/6-ways-to-tell-if- safe-the-scaled-agile-framework-is-right-for-you/ (or just google “6 ways agile safe”) http://www.agilesparks.com/solutions/scaling-agile/