Smart Scaling (ASK) presentation(agile2014)
•Transferir como PPTX, PDF•
3 gostaram•969 visualizações
Agile2014 conference presentation on "Smart Scaling" - how to compare scaling approaches. Our Agile Scaling Knowledgebase (ASK) and Decision Matrix help provide an objective way to compare approaches.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a Smart Scaling (ASK) presentation(agile2014)
Semelhante a Smart Scaling (ASK) presentation(agile2014) (20)
Mais de Richard Dolman
Mais de Richard Dolman (8)
Último
Último (20)
Smart Scaling (ASK) presentation(agile2014)
- 1. + ©2014 agilescaling.org - All rights reserved. SMART SCALING Finding the right approach for your organization Agile Scaling Knowledgebase ASK Agile2014 Orlando
- 2. ©2014 agilescaling.org - All rights reserved. + Steve Spearman Steve is an Agile Coach & Certified Scrum Trainer (CST) with a passion for happier teams, business improvement, and managing change. @sgspearman Introductions Richard Dolman Richard is an Agile Coach & Trainer passionate about empowering & enabling collaborative, high- performing teams and fostering organizational agility. @richarddolman 2
- 3. ©2014 agilescaling.org - All rights reserved. + Scrum Coach Retreat How we got started… 3
- 4. ©2014 agilescaling.org - All rights reserved. + ASK What is your definition of “Scaling”? What are you looking for in this session? 4 What is common among scaling approaches?
- 5. ©2014 agilescaling.org - All rights reserved. + ASK Decision Matrix 5 This is just a starting point. This is evolving – case in point – adding in “Scrum at Scale”. Users of this tool are encouraged to extend it.
- 6. ©2014 agilescaling.org - All rights reserved. + 6 Survey Results 70.8% Yes – keep it simple 12.5% No – I would Add more values 16.7% - Other, I would do something else We did change the actual colors based on comments
- 7. ©2014 agilescaling.org - All rights reserved. + Insights into Scaling Approaches Each of the popular Scaling Approaches offers a certain value proposition, focus, options for implementation, cost implications, and other attributes 7
- 8. ©2014 agilescaling.org - All rights reserved. + Input from Thought Leaders “Large-Scale Scrum (LeSS) is Scrum applied to many teams working together on one product. So one way of answering the question is, ‘the same focus as Scrum’, though that skirts a concrete answer.” - Craig Larman “Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning- oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.” - Scott Ambler “Spotify's approach to agile scaling is not really about our process or structure, it's all about the culture.” “…[it] approach will probably be unsuitable in organizations that are culturally very different…” - Henrick Kniberg “SAFe values business and practitioner outcomes over ideology, theory, framework, practice, or method. ” “You are doing something that will get a lot of heat from multiple directions, that probably means it is something worthwhile...” - Dean Leffingwell 8
- 9. ©2014 agilescaling.org - All rights reserved. + Insights - Spotify Spotify offers a culture-centric approach to Scaling Agile 9 With growth & multiple teams (over 50 Squads in 4 Cities), “Scrum was getting in the way more than it was helping”. Agile > Scrum Principles > Practices Squads have end-to-end autonomy over their Product(s) Loosely Coupled, Tightly Aligned Infrastructure Client Applications Features Self-Service, Open Source model Focus on Enabling each other Release Train Squads = Scrum Teams Chapters = Competency Areas Tribes = Light-weight Matrix of Squads & Chapters Guilds = Communities of Practice
- 10. ©2014 agilescaling.org - All rights reserved. + Insights - Spotify 10
- 11. ©2014 agilescaling.org - All rights reserved. + Insights - Spotify 11
- 12. ©2014 agilescaling.org - All rights reserved. + Insights - LeSS … Large Scale Scrum 12 Documented in two books (and a 3rd coming soon) Avoids a recipe of defined process – suggests “experiments” Believes each team and product must inspect and adapt their own Scrum adoption 2 suggested org structures for Up to 10 teams “Many” teams In a recent posting, Craig Larman characterized LeSS as: an *organizational design*, based on the thinking tools of: systems thinking, lean thinking, queuing theory, empirical process control, team and org design research
- 13. ©2014 agilescaling.org - All rights reserved. + Insights - LeSS 13
- 14. ©2014 agilescaling.org - All rights reserved. + Insights - LeSS 14
- 15. ©2014 agilescaling.org - All rights reserved. + Insights - DAD DAD seeks to extend Scrum for enterprise scale challenges 15 People-first, learning-oriented hybrid agile approach Risk-value delivery lifecycle and goal driven Agility at Scale is about explicitly addressing the complexities teams face in the real world. Key Steps: 1. Focus on consumable solutions, not just potentially shippable software 2. Extend Scrum’s construction lifecycle to address the full delivery lifecycle 3. Move beyond method branding 4. Adopt explicit governance strategies 5. Take a goal-based approach to enable scaling Promotes Enterprise Awareness Key Differentiator - explicitly recognizes that agile teams are governed
- 16. ©2014 agilescaling.org - All rights reserved. + Insights - DAD 16
- 17. ©2014 agilescaling.org - All rights reserved. + Insights - DAD 17 If you can’t beat ‘em, enable ‘em…
- 18. ©2014 agilescaling.org - All rights reserved. + Insights - SAFe …Scaled Agile Framework 18 Is applicable whenever at least a few hundred software practitioners are working cooperatively on related products & solutions Has generated great amounts of interest from enterprises Is becoming supported by a large number of Agile tools The SAFe “big picture” has 3 levels: portfolio, program, team Relatively more prescriptive, pragmatic And more controversial…. Evolving, growing, doing more types of training Release Trains
- 19. ©2014 agilescaling.org - All rights reserved. + Insights - SAFe 19
- 20. ©2014 agilescaling.org - All rights reserved. + Insights - SAFe 20
- 21. ©2014 agilescaling.org - All rights reserved. + 21 Sample Scenarios
- 22. ©2014 agilescaling.org - All rights reserved. + 22 Table Talk
- 23. ©2014 agilescaling.org - All rights reserved. + 23 www.agilescaling.org You’ll be able to download an editable version of the matrix. We’ll continue to add verbatim comments on the various frameworks to the website We just added a special area for comments from the authors We'll continue to reference case studies about use of the different frameworks and links to other key articles and scaling sites Other frameworks will be added to a special page of the website We'll continue to evolve the matrix and the site based on what YOU, the Agile Community, tell us What else…
- 24. ©2014 agilescaling.org - All rights reserved. + Conclusion Join the community and contribute to the knowledge sharing at www.agilescaling.org Q&A Thank You 24
Notas do Editor
- Steve + Richard Keep intro short – dive into Connections
- Steve Briefly explain origins – Concept emerged from Scrum Alliance Scrum Coach Retreat - December 2013 Original workshop members include: Richard Dolman, Steven Spearman, Dave Cornelius, Bob Galen, Bryan Stallings, Perry Reinert, Mike Register, Bill Johnson, and Vijay Kumar
- Richard + Steve Connections – Have audience introduce themselves to their table mates. Have them think about the topic and connect to it before we get into background and details. Each person will likely have some pre-conceived ideas of what “Scaling” means to them. These may be voided or validated through this session. Have Post-its and/or sheets of paper and sharpies. We should also have flip charts in the room. More teams? Bigger teams? Bigger problems? Bigger programs? Bigger dependencies? Across the organization? Beyond IT / SW development?
- Steve + Richard Review evolution and aspects of the “Matrix” Hand outs… The matrix is not intended to be a definitive or limited tool. Users may add or remove frameworks and criteria as needed. Mention Scrum at Scale (Brown/Sutherland); Enterprise Agile Transformation Framework (Michael Spayd); EbM (Scrum.org); Comparative Agility (Cohn); Agility Health (Elatta); others…
- Steve Review Survey results Format Ratings Levels
- Steve + Richard Discuss Insights/Learning for each of the popular approaches: Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve + Richard We reached out to each of authors of the primary Scaling approaches to get their take on this initiative as well as details about their approaches. Review input from Thought Leaders
- Richard Discuss Insights/Learning for Spotify Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Richard Discuss Insights/Learning for Spotify Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Richard Discuss Insights/Learning for Spotify Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve Discuss Insights/Learning for LeSS Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve Discuss Insights/Learning for LeSS Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve Discuss Insights/Learning for LeSS Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Richard Discuss Insights/Learning for DAD Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations. Extends Scrum for the entire lifecycle. “The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.” A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams. DAD Agile Lifecycle, as well as DAD Lean Lifecycle
- Richard Discuss Insights/Learning for DAD Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations. Extends Scrum for the entire lifecycle. “The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.” A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams. DAD Agile Lifecycle, as well as DAD Lean Lifecycle
- Richard Discuss Insights/Learning for DAD Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS DAD is a governed, hybrid approach that provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations. Extends Scrum for the entire lifecycle. “The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.” A differentiator of the DAD framework is that it explicitly recognizes that agile teams, just like other types of teams, are governed Enterprise awareness is one of the key aspects of the DAD framework. The observation is that DAD teams work within your organization’s organizational ecosystem, as do all other teams. DAD Agile Lifecycle, as well as DAD Lean Lifecycle Key Steps: 1. Focus on consumable solutions, not just potentially shippable software 2. Extend Scrum’s construction lifecycle to address the full delivery lifecycle 3. Move beyond method branding 4. Adopt explicit governance strategies 5. Take a goal-based approach to enable scaling
- Steve Discuss Insights/Learning for SAFe Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve Discuss Insights/Learning for SAFe Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Steve Discuss Insights/Learning for SAFe *Point out need to measure. Transition into other “orthogonal” measurement-centric models – including EbM, Comparative Agility, Agility Health, etc… Richard – Discuss DAD and Spotify Steve – Discuss SAFe and LeSS
- Scenario 1: “Traditional” / non-technology oriented, brick & mortar company IT org size approx 1000 Multiple Dev teams, plus “Shared Services” teams of DBAs, Security, Infrastructure, Specialized Developers Complex eco-system w/ combination of COTS and Custom App Dev Some co-located teams, but most are distributed, including outsourced/vendor teams Project-centric structure and strategy Command & Control culture Scenario 2: Medium-sized “technology” company IT org size of > 500 < 1000, but IT is the business Products are web-based, Saas-based Mostly co-located teams, but org is distributed Product-centric structure and strategy Predominately a Collaborative culture Scenario 3: Medium-sized company IT org size of > 500 Still relatively new to Agile, but looking to scale quickly Need to go from a few independent teams to several, cross-dependent teams Need to better coordinate release management Predominately a Competency culture
- Richard Concrete Practices – 15 Minutes (10 min + 5 min) Have handout of ASK Matrix for people to use, markup, discuss… Ask Questions about the Approaches and/or what challenges YOUR Organization may be facing. Hands-on exercise and/or table talk will build on concepts and provide mechanism for input/feedback. Have Post-its and/or sheets of paper and sharpies. We should also have flip charts in the room. ** Allow a few minutes for group discussion, key take-aways…
- Steve + Richard Talk about main next steps
- Steve + Richard Conclusion – Summarize ideas, feedback from audience and open Q&A to close.