Scrum

Scrum is an Agile framework for managing complex work that organizes teams into fixed-length iterations called sprints, with defined roles (Product Owner, Scrum Master, Developers) and ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective).

Category: General (also: Software Engineering, Business)

Author: Atomic Glue Technical Team

## Definition

Scrum is a lightweight Agile framework designed to help teams deliver value incrementally in a collaborative, self-organizing environment. Created by Ken Schwaber and Jeff Sutherland, Scrum was formally defined in the Scrum Guide (first published in 2010, updated through 2020). The framework is built around a small set of rules: one Product Backlog, one Sprint Backlog, one potentially releasable Increment at the end of each Sprint, and five events. Scrum is founded on empiricism: transparency, inspection, and adaptation. It is intentionally minimal; teams apply the framework and then adapt practices around it based on their specific context.

## Scrum Roles

Scrum defines three accountabilities: * **Product Owner:** Responsible for maximizing the value of the product. They manage the Product Backlog, prioritize work, and ensure that the team is working on the most valuable items first. * **Scrum Master:** Serves the team by ensuring Scrum is understood and enacted. They facilitate Scrum events, remove impediments, and coach the team in self-organization. * **Developers:** The people who do the work of creating the Increment each Sprint. They are self-organizing, cross-functional, and collectively accountable for delivering the Sprint Goal.

## Scrum Ceremonies (Events)

Scrum prescribes five events, each with a specific purpose: * **Sprint:** A fixed-length iteration (typically 2 weeks) during which a usable Increment is created. * **Sprint Planning:** The team selects Product Backlog items to work on and defines a Sprint Goal. * **Daily Scrum:** A 15-minute daily meeting where Developers inspect progress toward the Sprint Goal and adjust the plan. * **Sprint Review:** The team presents the Increment to stakeholders and gathers feedback. * **Sprint Retrospective:** The team inspects itself and creates a plan for improvements in the next Sprint.

## Scrum Artifacts

Scrum uses three core artifacts: * **Product Backlog:** An ordered list of everything that might be needed in the product. It is dynamic and constantly updated by the Product Owner. * **Sprint Backlog:** The set of Product Backlog items selected for the current Sprint, plus a plan for delivering them. * **Increment:** The sum of all completed Product Backlog items during a Sprint, combined with the increments of all previous Sprints. Each Increment must be usable and potentially releasable.

## Common questions

Q: What is the difference between Agile and Scrum?

A: Agile is the philosophy. Scrum is a framework that implements Agile principles. You can be Agile without Scrum, but Scrum is the most common way teams adopt Agile.

Q: How long should a Sprint be?

A: One month or less. Two weeks is the most common. The length should be consistent across Sprints; never vary it.

Q: Is a Scrum Master a project manager?

A: No. A Scrum Master is a servant-leader and coach, not a manager. They do not assign tasks or hold people accountable for delivery. The team is self-organizing.

## Key takeaways

• Scrum is a lightweight Agile framework with defined roles, events, and artifacts.
• Three accountabilities: Product Owner, Scrum Master, Developers.
• Five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
• Scrum is founded on empiricism: transparency, inspection, adaptation.

## Related entries

• [Agile Development](atomicglue.co/glossary/agile-development)
• [Sprint](atomicglue.co/glossary/sprint)
• [Roadmap](atomicglue.co/glossary/roadmap)
• [Technical Debt](atomicglue.co/glossary/technical-debt)

Last updated July 2025. Permalink: atomicglue.co/glossary/scrum