What is Scrum?
Scrum is the most widely adopted Agile framework. It structures product development around fixed-length iterations called sprints (usually one to two weeks), each producing a potentially shippable increment.
Scrum defines three roles — the Product Owner (owns the backlog and priorities), the Scrum Master (facilitates the process and removes blockers), and the Development Team (builds the increment). It also prescribes a set of ceremonies: sprint planning, the daily standup, the sprint review, and the retrospective.
Product managers often act as or work closely with the Product Owner in a Scrum setup. Understanding Scrum well matters because it governs the cadence of decision-making: what gets committed to a sprint, how scope changes are handled, and how the team inspects and adapts each cycle.
Examples
- A team runs two-week sprints, demos completed work in a sprint review every other Friday, and holds a retro to improve their process.
- A Product Owner refines and reprioritizes the backlog before each sprint planning session.
Where PMs use this
Related terms
Agile
An iterative approach to building products that delivers value in small, frequent increments instead of one large release.
Sprint
A fixed, short period (typically 1–2 weeks) during which a Scrum team completes a set of committed work.
Product Owner
A Scrum role responsible for maximizing product value by owning and prioritizing the backlog.
Scrum Master
A Scrum role that facilitates the process, coaches the team, and removes impediments to progress.
Retrospective
A recurring team meeting to reflect on the last sprint and identify concrete process improvements.
Product Backlog
A prioritized, continuously updated list of everything that might be built for a product.