Scrum is a lightweight Agile framework in which a small team delivers work in time-boxed sprints, guided by a product owner who prioritizes the backlog and a Scrum Master who helps the team follow the process.
Why it matters
Scrum gives teams a predictable cycle: plan, build, review, improve. Its roles and events make responsibility clear and expose obstacles quickly. It suits work that can be broken into small pieces and benefits from regular feedback. The three Scrum roles are product owner, Scrum Master and developers, and the main events are sprint planning, daily scrum, sprint review and sprint retrospective.
Example
A four-week example: sprint planning on Monday selects 10 backlog items; a 15-minute daily scrum keeps the team in sync; the sprint review shows finished work to stakeholders; the retrospective picks one process change to try next sprint.
Common mistakes
- Using Scrum meetings without a prioritized backlog.
- Making the Scrum Master a project manager who assigns tasks.
- Letting sprints run long because work was not broken down.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.