This document discusses scaling agile frameworks, specifically LeSS (Large-Scale Scrum). It describes two frameworks - one for up to 10 teams and another for up to 100 teams. The second framework involves dividing the product backlog into multiple area backlogs. An example project is provided of developing a CRM system for a mobile telco with over 80 people on 7 Scrum teams and nearly 1000 user stories while integrating with 20 legacy systems.

1. Scaling Agile with
#LeSS
@marekkirejczyk

3. Scaling Scrum
with LeSS

4. First Rule of Scaling
Scrum: Don’t!

5. FRAMEWORK 1:!
Up to 10 teams

6. Roles

7. SCRUM vs. LeSS

8. Team

9. Product Owner

10. Artefacts

11. Product Backlog

12. Product Increment

13. Ceremonies

14. Sprint Plannings

15. Daily stand-up

16. Sprint Review

17. Sprint Retrospective

18. Community of interests
Design Architecture
Integration UX

20. FRAMEWORK 2:!
Up to 100 teams

21. Backlog
Product Backlog Area Backlogs

23. EXAMPLE

24. CRM for mobile telco
• CRM
• Order Management
• Integration via EAI Tibco
• Legacy customisation (eg. Billing, Business
intelligence)
• Integration with Central Product Catalog, Scoring

25. CRM for mobile telco
• SCRUM for greenfield and waterfall for legacy
• Over 80 people in Scrum teams
• Over 7 Scrum teams
• Nearly 1000 User Stories

26. Corporate constraints
• Relatively short project lifespan
• Integration with ~20 legacy systems
• Classic management layer
• Distributed team
• Corporate polices

27. Daily stand-up
Generic development
teams Specialised teams
Integration
team
Architect
team
Managers
team
Product
Owners

28. Thank you
@marekkirejczyk