An Agile framework for delivering work in short, fixed-length cycles called sprints — typically one to four weeks — organized around daily standups, sprint planning, retrospectives, and reviews. For design teams, Scrum provides a rhythm for iteration and stakeholder feedback, though the sprint structure requires designers to work ahead of developers to prevent design from becoming a bottleneck.
Common contexts
- Establishing a 'design sprint N+1' practice so designers are always one sprint ahead of the development team in a Scrum workflow
- Negotiating design review slots within sprint ceremonies so design work gets feedback before it's too expensive to change
- Mapping research activities to sprint cycles to show stakeholders how discovery work connects to upcoming sprint commitments
Use when
Work within Scrum when your team is already using it — resisting an established organisational process creates more friction than it resolves; instead, negotiate design's position within the framework to protect discovery and iteration time.
Avoid when
Don't force Scrum onto a small design team doing exploratory research — the ceremony overhead of standups, sprint planning, and retrospectives consumes a disproportionate share of time for a team of one or two where informal communication works better.
Scrum's biggest challenge for designers isn't the cadence — it's the implicit pressure to deliver something visually complete every sprint, which pushes teams toward polished designs of the wrong thing rather than rough explorations of the right direction.
Real-world examples
- Spotify's squad model is built on Scrum but replaces the traditional Scrum Master role with an 'Agile Coach' shared across multiple squads, a structural adaptation now taught in Agile certifications worldwide.
- Google's early Gmail team ran 2-week Scrum sprints during the 2004 beta period, shipping a new feature every fortnight — a cadence that generated 100+ features in the first year and established Gmail as an innovation benchmark.
- Atlassian's Jira is used by 65,000+ companies to run Scrum ceremonies, making it the most widely deployed Scrum board tool and the de facto standard for connecting sprint planning to product roadmap.