Before you start Scaling (Scrum)
0 likes856 views
The document discusses the key considerations and strategies for scaling Agile practices, particularly focusing on the concept of 'Scaled Scrum.' It highlights the necessity of preparation, clear objectives, and the importance of managing dependencies and integrations effectively to avoid potential pitfalls. Additionally, it emphasizes the need for measuring outcomes and choosing appropriate frameworks to ensure successful scaling without creating chaos.
Before you start Scaling (Scrum)
- 1. @krystian_kaczor BEFORE YOU START SCALING 1 BEFORE YOU START SCALING Agile By Example 2019 © QAgile 2019 v. 1.0 @QAgile_plwww.qagile.plfb.me/qagilepl
- 2. @krystian_kaczor BEFORE YOU START SCALING 2 Scaling, Transformation WHAT IS SCALING?
- 3. @krystian_kaczor BEFORE YOU START SCALING 3 SCALING – WHAT DO YOU MEAN? # OF TEAMS # OF PRODUCTS 1 >1 1 >1 Scaled Scrum Scrum Portfolio / Agile Transformation Context Switching Today let’s focus here
- 4. @krystian_kaczor BEFORE YOU START SCALING 4 YOU WANT MORE OF VS YOU ALSO GET MORE OF • Output • Impact • Shorter T2M • Revenue • Process overhead • Dependencies • Integration issues • Defects • Problems with bottlenecks • Impediments • Bad Scrum implementation
- 5. @krystian_kaczor BEFORE YOU START SCALING 555 Scaled Scrum is still Scrum
- 6. @krystian_kaczor BEFORE YOU START SCALING 6 What do you want to achieve? WHY TO SCALE
- 7. @krystian_kaczor BEFORE YOU START SCALING 7 REASONS FOR SCALING 1. We want to go faster 2. Our product is really big 3. Our business is growing
- 8. @krystian_kaczor BEFORE YOU START SCALING 8 WE WANT TO GO FASTER 1. How fast is faster? 2. Do you need scaling to go faster? 3. What’s your hypothesis? 4. Does adding teams pay off? Velocity Teams • If we release 2 months earlier we will make 500k more (Cost of Delay) • If we add 2 teams more with the current Product Backlog we will make it in 3 months • The cost of 2 additional teams for 3 months is 600k Does it make sense?
- 9. @krystian_kaczor BEFORE YOU START SCALING 9 or … PREPARE TO SCALE
- 10. @krystian_kaczor BEFORE YOU START SCALING 10 NOT THAT WAY – MODERN WATERFALL Customer Journey/ Design Thinking/ UX & UI FESEABILITY Arch, Solution USER STORIES SPRINTS UAT DEV OPS T2M?
- 11. @krystian_kaczor BEFORE YOU START SCALING 111111 Scaled Scrum is still Scrum
- 12. @krystian_kaczor BEFORE YOU START SCALING 12 HOW TO ORGANIZE SCALING PRODUCT TEAMS ARCHITECTURE Support value delivery Supports the teams, enables fast releasing
- 13. @krystian_kaczor BEFORE YOU START SCALING 13 HOW ARE YOU GOING TO 1. … define and manage goals (OKRs, strategy, Release Goal, Sprint Goal) 2. … slice the product? (features, areas, personas) 3. … the manage Product Backlog? (structure) 4. … scale Product Owner role? (up, down, Product Owner team, UX, Vision) 5. ... align process? (events, estimation) 6. ... scale removing impediments? (escalation path) 7. ... align standards (Scrum, DoD, architecture) 8. ... manage dependencies? (visualization, solving) 9. ... integrate and release? (infrastructure, repository, tools) 10. ... align between teams? (SoS, SDS, NIT) 11. ... add more teams? (team growth, domain knowledge, skills)
- 14. @krystian_kaczor BEFORE YOU START SCALING 14 USE SCALING FRAMEWORKS
- 15. @krystian_kaczor BEFORE YOU START SCALING 15 MEASURE AND MANAGE
- 16. @krystian_kaczor BEFORE YOU START SCALING 16 Before you scale SUMMARY
- 17. @krystian_kaczor BEFORE YOU START SCALING 17 BEFORE YOU START SCALING 1. Scaling means scaling the good things and the bad things 2. Create thesis/business case 3. You need to do it well to be successful 4. Without preparation you can cause chaos and full stop - Prepare well 5. Choose framework instead of reinventing a wheel 6. Measure and manage on the way 7. Scaled Scrum is still Scrum
- 18. @krystian_kaczor BEFORE YOU START SCALING 18 THANK YOU Krystian Kaczor krystian@qagile.pl @krystian_kaczor @QAgile_plwww.qagile.p l fb.me/qagile pl