Scaling Scrum in Fully Remote Work — Challenges from 3 People to 30 People and 6 Teams over Three Years and Applying Scrum@Scale and LeSS Practices
summary
A practical case study of scaling a fully remote Scrum organization from 3 to 30 people over three years while delivering a browser GPU materials simulator (claimed >10,000× faster). Describes starting with a Jupyter‑notebook Python MVP, splitting into research/core‑tech and service teams, then forming two cross‑functional squads and ultimately six teams with three product backlogs and one sprint review. Explains using Slack and small five‑person meetings to cut coordination overhead, keeping teams at ~5–7 people, avoiding rigid ownership, and applying Scrum@Scale and LeSS practices to preserve a loose research cadence.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:43Product and company
- 3:37Scrum@Scale and LeSS
- 4:20One team start
- 6:51Three teams growth
- 8:58Service team splits
- 11:52PO and team roles
- 14:03Team division summary
- 15:09Remote work challenges
- 17:35Remote meeting tips
- 18:38Final recommendations
