Uploaded byNilesh Kulkarni
Why one size doesnt fit all
This document discusses selecting a scaling framework for agile organizations. It describes several popular frameworks like SAFe, LeSS, and Spotify and criteria for choosing one, like the type of organization, training complexity, and cultural fit. Key aspects of scaling agile include changing organizational structures, communication practices, engineering practices, and product management roles. The document advocates for an incremental rollout approach starting with a pilot program and evolving the implementation over time through metrics and feedback.
More Related Content
Similar to Why one size doesnt fit all
Why one size doesnt fit all
- 1. Why one sizedoes not fit all - Selecting Scaling Frameworks Nilesh Kulkarni, Program Manager and Agile Coach CSM, CSPO, CSP, PMP, PMI-ACP, SAFe SPC 4.0, LeSS CLP, TKP Email - nileshrk@gmail.com Twitter @nileshrk1 Linkedin: https://in.linkedin.com/in/nileshrk
- 2. Copyright © 2015Allscripts Healthcare Solutions, Inc. 2 Which scaling framework is best in the Industry?
- 3. Copyright © 2015Allscripts Healthcare Solutions, Inc. 3 Framework shopping cart SAFe LeSS Nexus Spotify DAD Scrum at scale Enterprise scrum SLIM, SCARE, FAST-Agile, many more
- 4. Copyright © 2015Allscripts Healthcare Solutions, Inc. 4 Scaled agile framework http://scaledagileframework.com/
- 5. Copyright © 2015Allscripts Healthcare Solutions, Inc. 5 5 LeSS framework http://less.works/
- 6. Copyright © 2015Allscripts Healthcare Solutions, Inc. 6 According to you: • What is agile? • What is scaling? • What is scaling agile?
- 7. Copyright © 2015Allscripts Healthcare Solutions, Inc. 7 Are all organizations really same?
- 8. Copyright © 2015Allscripts Healthcare Solutions, Inc. 8 Where to start • What is organization need? • Which framework we can use? • Where do we start implementation? • What about tools? • What about other organizational aspects?
- 9. Copyright © 2015Allscripts Healthcare Solutions, Inc. 9 Criteria for selecting the framework • Suitable for what type of org? • Is it only focused on software development teams only? • Training complexity • Can you implement on your own? • Is it suitable for your org culture? • Others?
- 10. Copyright © 2015Allscripts Healthcare Solutions, Inc. 10 Driving principles • Deliver value quickly • Simplicity • Keep scaling implementation itself agile. • Don’t make it waterfall! You can implement it over time. • Scaling can include descaling some practices • Make best use of everything.
- 11. Copyright © 2015Allscripts Healthcare Solutions, Inc. 11 Organizational structure changes –Workspace design –Team structure • Co-located teams • Group them at same location based on functional area • How to scale with distributed teams
- 12. Copyright © 2015Allscripts Healthcare Solutions, Inc. 12 Scaling communication • Scrum of scrum/ synchronization events • Scaling backlog refinement sessions • Scaling planning sessions • Scaling demos • Retrospectives
- 13. Copyright © 2015Allscripts Healthcare Solutions, Inc. 13 Scaling engineering practices • All teams work on same codebase • CI • CD • Automation • Delivering value continuously needs continuous integration beyond technology.
- 14. Copyright © 2015Allscripts Healthcare Solutions, Inc. 14 Scaling Product Management role • Agile Product roadmap • Product management role need to be scaled appropriately • Area PO concept from LeSS
- 15. Copyright © 2015Allscripts Healthcare Solutions, Inc. 15 Roll out plan • Training • Coaching • Readiness plan • Selecting a pilot program • Putting structure in place • Scaling roles – Keep it simple and straight
- 16. Copyright © 2015Allscripts Healthcare Solutions, Inc. 16 Implement the plan • How do we know if we are scaling in right direction? – Measures – Metrics – Trends – Surveys – Retrospectives – Fail early, fail fast
- 17. Copyright © 2015Allscripts Healthcare Solutions, Inc. 17 Grow and evolve • How to spread it within the organization • Program level • Portfolio level • Enterprise level • Re-evaluate
- 18. Copyright © 2015Allscripts Healthcare Solutions, Inc. 18 References • Scaled agile framework http://scaledagileframework.com/ • LeSS http://less.works/ • Nexus guide https://www.scrum.org/resources/nexus-guide?gclid=CjwKEAiA0fnFBRC6g8rgmICvrw0SJADx1_zAsz-J4hE3WPUZV30cjY4oI6wn4iYtixApM- XmVWDsURoC6u_w_wcB • DAD http://www.disciplinedagiledelivery.com/ • ASK metrics http://www.agilescaling.org/ask-matrix.html
- 19. Copyright © 2015Allscripts Healthcare Solutions, Inc. 19 Email: nileshrk@gmail.com Twitter: @nileshrk1 Linkedin: https://in.linkedin.com/in/nileshrk
Editor's Notes
- #3 Which scaling framework is best in the Industry? This question is similar to asking a question do we have one size clothes or shoes that will fit anybody in this universe? Answer is there is no best framework. There are frameworks which are suitable for particular organizations. Or to be more specific, we have certain practices in each framework what can work in your environment, culture and will fit your needs.
- #4 SLIM – scrum lean in motion - from growing agile SCARE – sustainable cultural agile release for enterprise FAST Agile
- #7 Agile means different things to different people. Agile = scrum, or any methodology, agile means cultural change, agile means new process, agile is mindset and so on Scaling means different things as well. Do the same thing on larger scale? Replicate agile from 1 team to multiple teams, scale it from development org to other functions, horizontal scaling or vertical scaling Scaling agile What is scaling agile for your org It is about delivering big programs Is it about spreading agile implementation in other functions For some people, scaling agile in business functions Scaling agile means scaling beyond IT
- #9 Need? Driven by client request? Multiple programs? Distributed teams? Market needs? Time to market? Frequent delivery? Where to start Creating light weight roll out plan Selecting pilot program or big bang roll out Training needs Infrastructure needs Do you really need the tools Which tools can help you to change the culture
- #10 Team level Technical practices Cost of implementation Flexible/emergent/prescriptive Built on which basic frameworks Suitable for which type of orgs Is it software centric? Deployment approach?
- #11 Value to customer Value to organization Simplicity is decluttering products, processes. Do what is enough for today. Same applies when we go for scaling agile. These aspects are important when we select tools, frameworks etc Having minimum roles in org is simplicity Descaling – identify non value adding elements in the org and start trusting the teams more. Scale down non value adding processes and give people choice to find alternative.
- #18 Do your own research
- #22 Along with basics, new practices may be needed for program and portfolio level No single framework can solve all your problems but you can take best practices from all available frameworks