Abstract: The usual approach to scale Scrum is to start with one team as pilot then scale. This experience report provides a different approach. We focused on organization design first, without having proper Scrum implementation at team level. We used the main design elements from LeSS, but kept team level less changed. Then, we created demand to help some teams towards self-organization. We used the same approach in two different product units from the same company. The two units represented cases of different sizes, as cases of LeSS and LeSS Huge respectively.
Lessons Learned from Your Experience: - Organization first approach while scaling Scrum
- Incremental approach to expand domain specialization for more flexibility
- Transitional path from traditional Team Leader to SM/Coach
- Enable self-organization across teams via joint Scrum events
- Enable one PO vs. multiple teams by getting teams on requirement clarification and direct feedback with SMEs and users
Attachments: