Scrum

Scrum is the most widely used Agile framework — a small cross-functional team delivers work in fixed-length sprints, guided by three roles, three artefacts and a rhythm of five events.

Scrum is a lightweight framework for developing and sustaining complex products. Work is organised into sprints — fixed iterations, usually one to four weeks — each producing a potentially releasable increment. It defines three accountabilities (Product Owner, Scrum Master, Developers), three artefacts (Product Backlog, Sprint Backlog, Increment, each with a commitment: product goal, sprint goal, definition of done), and a set of events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective). Scrum is built on empiricism: transparency, inspection and adaptation.

Why it matters

Scrum gives Agile a concrete, repeatable structure. The fixed sprint cadence creates a reliable delivery heartbeat; the roles clarify who owns priorities (Product Owner) versus who owns the process (Scrum Master); the events guarantee planning, coordination, feedback and improvement happen regularly rather than being skipped. For teams new to Agile, Scrum’s prescriptiveness is a feature — it provides guardrails.

When to use it

Scrum suits complex product work that benefits from regular delivery and feedback, done by a stable team of roughly three to nine people. It fits less well for pure support/interrupt-driven work (Kanban is often better), for efforts too small to justify the ceremonies, or where a single fixed deadline dominates and iteration adds little.

How to use it

1. The Product Owner orders the Product Backlog by value.
2. In Sprint Planning, the team selects backlog items into a Sprint Backlog and sets a sprint goal.
3. During the sprint, the team builds the increment, coordinating daily in the 15-minute Daily Scrum.
4. At the Sprint Review, the team demonstrates the increment and gathers feedback that reshapes the backlog.
5. At the Retrospective, the team inspects how it worked and commits to improvements for the next sprint.

Example

A team runs two-week sprints. On day one they plan, pulling in the top backlog items for a sprint goal of "users can reset their password". They meet for 15 minutes each morning, demo the working feature at the review, and in the retro decide to add automated tests because a bug slipped through. Next sprint starts the cycle again.

Template

Scrum needs a product backlog, sprint backlog, a definition of done and a Scrum board; start from those templates and adapt.

Browse templates →

Tools

Related topics

FAQs

Alternatives

• Kanban — continuous flow instead of sprints
• Scrumban — hybrid of Scrum structure and Kanban flow
• XP (Extreme Programming) — Agile with strong engineering practices