More with LeSS
- 1. Achieving more with LeSS Reducing complexity at scale
- 2. More with Less Reducing complexity at scale Agenda 1. Introduction 2. What is Scrum? 3. What is LeSS? 4. Why LeSS? 5. Conclusion
- 3. • Agile enthusiast for 10 years • Scrum Master • LeSS Practitioner • Agile Coach for GP AU/NZ - largest non-Bank payments provider in AU/NZ • Co-Founder of Kaizen Agility Group - bringing agile training to Brisbane • What is an Agile Coach? • In my case: someone with an in-depth understanding of putting agile principles into practice – in particular Scrum – and real-world experience in actual ”agile” organizations. • Experience with guiding agility at the enterprise level, organisational agility transformations • Multiple team Scrum Master • In-depth understanding of agile frameworks including LeSS, Scrum, Lean, Kanban, XP About Me
- 4. Semi-Automatic Ground Environment (SAGE) was the first large-scale software intensive product development. It involved hundreds of developers and came in hugely late and over budget. When a director was asked: “If you had to do it all over again what would you do differently?” The background
- 5. He responded with... “Find the ten best people and write the entire thing themselves.” -Horowitz
- 6. So, How do you scale Agile ?
- 7. It’s the wrong question to ask
- 8. The question should be: How can we simplify the unnecessarily big and complex organizational design, and be agile rather than do agile?
- 9. Why are organisations overly complex?
- 10. Why is agility important?
- 11. Jeff Sutherland & Ken Schwaber Creators of Scrum LeSS Started with Scrum
- 12. Scrum is… “An agile framework that allows us to focus on delivering the highest business value in the shortest time.” Mike Cohn - “Introduction to Scrum Methodology” What is Scrum?
- 13. The Scrum Cycle + Sprint Planning Review Retrospective Backlog Refinement Team Definition of Done Daily Scrum Potentially Shippable Increment Sprint Backlog Product Backlog Product Owner Organisation Scrum Master User Stories Tasks +
- 14. Why Scrum?
- 15. Scrum hits the sweet spot between defined concrete elements and empirical process control There are no best practices. Only good practices within a specific context.
- 16. What is Large Scale Scrum (LeSS)
- 17. LeSS is a lightweight (agile) framework for scaling Scrum to more than one team.
- 18. LeSS consists of Principles, the framework, guides and a set of experiments
- 19. Try / Consider / Avoid 600 Experiments
- 20. LeSS is not More LeSS is a minimalistic scaled up version of one-team Scrum, and it maintains many of the practices and ideas of one-team Scrum. In LeSS, you will find: ● A single Product Backlog (because it’s for a product, not a team) ● One Definition of Done for all teams ● One Potentially Shippable Product Increment at the end of each Sprint ● One Product Owner ● Many complete, cross-functional teams (with no single-specialist teams) ● One sprint In LeSS all Teams are in a common sprint to deliver a common shippable product, every sprint.
- 21. LeSS Framework
- 22. Why LeSS?
- 23. For large groups, LeSS hits the sweet spot between defined concrete elements and empirical process control There are no best practices. Only good practices within a specific context.
- 24. LeSS Principles
- 25. LeSS Principles
- 26. LeSS Principles - Large-Scale Scrum is Scrum
- 27. LeSS Principles - More with LeSS
- 28. More with LeSS ● Less roles = more responsible teams ○ No “co-ordinators” ○ No project managers ○ LeSS Scrum Masters = up to 3 teams per SM ○ Teams are responsible for end to end to delivery ○ Teams are responsible for coordination
- 29. More with LeSS ● Less Product Owners = more decision rights ○ 1 voice for prioritisation across an entire customer area ○ 1 Product focus for an entire customer area ○ Many teams working with one Product Owner
- 30. More with LeSS ● Less priorities = More shared goals across the business ○ 1 Product Backlog per Customer Area ○ Customer areas are defined by Customer needs
- 31. More with LeSS ● Less priorities = More shared goals across the business ○ 1 Product Backlog per Customer Area ○ Customer areas are defined by Customer needs ○ Less priority conflicts ○ Less “disruptions”
- 32. More with LeSS ● Less artifacts = More Customer Centricity ○ documentation is fit-for-purpose ○ more frequent face to face collaboration ○ more frequent walk-throughs ○ more happy customers
- 33. More with LeSS ● Less supplied “best practice” = More team process ownership ○ teams continuously improve their process ○ teams adapt to change ○ more freedom ○ more decentralised decision making
- 34. 4. Conclusion
- 35. More with LeSS - in Summary ● Less is a “barely sufficient” framework ○ applied to many teams—Cross-functional, cross-component, full-stack feature teams of 3–9 learning-focused people that do it all—from UX to code to videos—to create done items and a shippable product. ○ …working together—The teams are working together because they have a common goal to deliver one common shippable product at the end of a common Sprint, and each team cares about this because they are a feature team responsible for the whole, not a part. ○ …on one product—What product? A broad complete end-to-end customer-centric solution that real customers use. It’s not a component, platform, layer, or library.
- 36. Me and Venky will be providing Certified LeSS Practitioner in May First LeSS training in Brisbane Located at Clifton’s in Brisbane CBD Bookings here: https://tinyurl.com/brisbane-less Get trained in May!