Scrum
Definition
Scrum
Scrum is a lightweight framework in which a small team delivers work in fixed-length cycles called sprints, then inspects the result and adapts at set points. Scrum tells a team when to look, not what to build, and that restraint is entirely deliberate.

The definition is not folklore. The Scrum Guide, the framework’s own specification and last revised in November 2020, calls it a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
It is small enough to be misread as simple. The guide names five events, three artifacts and three accountabilities, and says a Scrum team is typically 10 or fewer people.
Public-sector buyers increasingly audit against it. The Government Accountability Office’s September 2020 guide sets out best practices for assessing Agile adoption in federal programmes, where Scrum is the usual implementation.
Key takeaways
- Scrum runs work in sprints of one month or less, with fixed inspection points.
- The framework defines five events, three artifacts and three accountabilities — and nothing else.
- A Scrum team is typically ten people or fewer.
- Scrum is one way to implement agile, not a synonym for it.
How it works
Scrum closes a loop at known intervals. The sprint is the container, three artifacts hold the work and its goals, and the remaining four events exist to inspect something specific and adapt before the next cycle starts.
| Element | Name | Purpose or commitment |
|---|---|---|
| Event | Sprint | the container, one month or less |
| Event | Sprint Planning | agrees what the sprint will deliver |
| Event | Daily Scrum | re-plans the next day of work |
| Event | Sprint Review | inspects the increment with stakeholders |
| Event | Sprint Retrospective | improves how the team works |
| Artifact | Product Backlog | commits to the Product Goal |
| Artifact | Sprint Backlog | commits to the Sprint Goal |
| Artifact | Increment | commits to the Definition of Done |
The sprint length is a hard ceiling rather than a suggestion. One month or less keeps the cost of a wrong decision bounded, because nothing can run further than a single cycle before somebody looks at it.
Each artifact carries a commitment — which is the 2020 guide’s most underused idea. A backlog without a goal is a list, and a list cannot tell a team what to drop when the sprint is running late.

The three accountabilities are set out properly in scrum team roles, so this entry leaves them there rather than restating the cast. What matters here is that the framework names three and stops.
Sprint planning is where the loop opens, and it is the event most often reduced to task allocation. Done properly it produces a goal the team can still state on day eight.
Scrum implements the values described in agile methodology rather than replacing them. Teams that treat the events as a schedule, and skip the inspection the events exist for, get the ceremony without the feedback.
Nothing in the framework says how to build anything. There is no prescribed estimation technique, no engineering practice and no tooling, which is deliberate and is also why Scrum gets blamed for problems it never addressed.
The Daily Scrum is the most misread of the five events. It exists so developers can re-plan their own next day, not so a manager can collect status, and the difference shows within a fortnight.
A sprint can be cancelled, and almost never is. The guide permits it when the Sprint Goal becomes obsolete, which is a useful test of whether the goal was ever real.
Examples
Scrum is specified tightly enough that real implementations diverge in recognisable ways, usually by dropping whichever event is least comfortable. The four below include two that work and two that are Scrum in name.
A product team runs two-week sprints and ends each one with a working increment a stakeholder can click. This is Scrum doing its job, and the retrospective is the reason it keeps improving.
Without that event the team repeats the same friction every cycle. It then describes the friction as the nature of the work, which is how a fixable problem becomes a permanent one.
An offshore team in Bengaluru runs the full event set with a client in London. The scrum master offshore protects the sprint across a four-and-a-half-hour gap — which is a facilitation problem rather than a process one.
A team holds daily stand-ups and calls itself agile, but the sprint never produces anything releasable. The events survived and the increment did not — which is the commonest failure in the framework.
Scrum is unusually easy to perform and unusually hard to do. The events are visible to anyone walking past, while the inspection they exist for is not.
A programme runs eight teams on a shared cadence through an agile release train. Each team runs Scrum internally while the train handles the dependencies between them.
Related terms
Scrum sits between a broader philosophy above it and a cast of specific roles and events below it. The entries below occupy those neighbouring levels, so none of them is another description of the framework itself.
- Scrum Team Roles: the three accountabilities that make up a Scrum team.
- Sprint Planning: the event that opens a sprint and agrees its goal.
- Agile Methodology: the values and principles Scrum puts into practice.
- Scrum Master Offshore: the facilitator role delivered from a remote hub.
- Agile Release Train: several agile teams releasing on one shared cadence.
- Software Development Outsourcing: contracted engineering capacity, frequently staffed as Scrum teams.
FAQ
How long is a sprint?
One month or less, which the Scrum Guide states as a ceiling rather than a target. Two weeks is the most common choice in practice.
Is Scrum the same as agile?
No. Agile is a set of values and principles; Scrum is one framework that implements them. A team can be agile without Scrum, and can run Scrum without being agile.
How big should a Scrum team be?
Typically ten people or fewer, according to the 2020 guide. Larger groups are split into several teams working from one Product Backlog.
What does Scrum deliberately leave out?
Almost everything about how the work is done. It specifies no engineering practices, no estimation technique and no tooling, which is why two Scrum teams can look nothing alike.
Who decides what goes into a sprint?
The developers decide how much they can take on, and the Product Owner decides what matters most. Neither side decides alone, and that split is the point of the arrangement.
Does Scrum work with an offshore team?
Yes, where the time zones overlap enough for a daily conversation and the team holds real decision rights. Find providers running Scrum delivery teams on Outsource Accelerator.







Independent




