# Scrum

A lightweight framework in which a small, self-managing team delivers usable increments, inspects results, and adapts its plan around a Product Goal.

- Type: framework
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/scrum/>)

## What it means

Scrum is a framework for generating value while addressing complex problems. A Product Owner orders work, Developers create a usable Increment during a Sprint, and a Scrum Master helps the team and organization use Scrum effectively. Its accountabilities, events, and artifacts create regular opportunities for transparency, inspection, and adaptation.

## Why it matters

Product work contains uncertainty about needs, solutions, and feasibility. Scrum limits the planning horizon, makes progress visible through working increments, and gives teams recurring moments to learn from stakeholders and improve how they work rather than defending a fixed long-range plan.

## When to use it

Use Scrum when a stable cross-functional team owns a complex product problem and can deliver meaningful increments at least monthly. It fits poorly when work is mostly interrupt-driven, dependencies prevent an integrated increment, or leaders will not give the team authority to adapt scope and methods.

## How it works

1. Set a Product Goal and maintain an ordered Product Backlog of possible work.
2. At Sprint Planning, choose a valuable Sprint Goal and build a realistic Sprint Backlog.
3. Collaborate daily, inspect progress, and adjust the plan without endangering the Sprint Goal.
4. Create at least one usable Increment that meets the shared Definition of Done.
5. Inspect the product with stakeholders at the Sprint Review and adapt the backlog.
6. Improve quality and team effectiveness through the Sprint Retrospective.

## A practical example

A payroll team works in two-week Sprints toward reducing failed employee onboarding. It releases a validated bank-detail check, reviews support and completion data with operations, then changes the next Sprint’s plan when the evidence shows international account formats are the larger obstacle.

## Where it breaks

Scrum does not supply product strategy, discovery methods, engineering practices, or a guarantee of agility. Teams can follow every event while shipping low-value work. Fixed individual assignments, weak product ownership, and increments that cannot be released turn the framework into meeting theater.

## Common mistakes

- Treating the Sprint as a promise to complete every selected backlog item.
- Using the Scrum Master as a project coordinator or team manager.
- Skipping a usable Increment and calling partially integrated work done.
- Excluding customers and stakeholders from meaningful inspection.

## Sources

1. [The Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [What Is Scrum?](<https://agilealliance.org/glossary/scrum>) — Agile Alliance · Professional glossary

## Related topics

- [Sprint Planning](<https://wiki.soroush.uk/topic/sprint-planning/>)
- [Sprint Review](<https://wiki.soroush.uk/topic/sprint-review/>)
- [Retrospective](<https://wiki.soroush.uk/topic/retrospective/>)
