Scrum is a lightweight framework for delivering complex work in fixed-length iterations called sprints, with three accountabilities, five events and three artefacts, defined in a short public guide.
Our take. Scrum is thirteen pages long and most of what is done in its name is not in them. Daily meetings that are status reports, sprints that are two-week waterfalls, a Scrum Master who is a project manager with a new title: the guide forbids or omits all of these, and the certifications test the guide. Read the thirteen pages before deciding whether your team does Scrum.
Three accountabilities: the Product Owner, who orders the backlog and is accountable for value; the Developers, who build the increment; the Scrum Master, who is accountable for the framework being understood and effective. No project manager, no team lead, no tester as a separate role.
Five events: the sprint, a fixed container of a month or less; sprint planning at its start; the daily scrum, fifteen minutes for the Developers to plan their day; the sprint review, where the increment is shown to stakeholders; the sprint retrospective, where the team improves how it works.
Three artefacts, each with a commitment: the Product Backlog and its Product Goal; the Sprint Backlog and its Sprint Goal; the Increment and its Definition of Done.
That is the framework, and the guide that defines it is deliberately incomplete: it says what must exist and leaves how to the team. The gaps are where practice diverges from the text. Story points, velocity, user stories, burn-down charts, refinement meetings and the phrase sprint zero appear nowhere in the guide; they are practices teams have adopted around it, some useful and some not, and the assessments the certifying bodies run test the guide rather than the practices. That is why seasoned practitioners fail the entry assessment: they answer from their team's Scrum, and the questions are about the written one.
The framework's real content is in its constraints. The sprint length does not change once set, so the team learns to size work to the container. The Sprint Goal does not change during the sprint, so a stakeholder with an urgent idea waits, at most, a month. One person orders the backlog, so scope is a decision and not a negotiation. The daily scrum belongs to the Developers, so it is not a status report to anyone. Each of those is violated constantly in practice, and each violation removes the reason the framework exists, which is to make the cost of changing direction visible and bounded.
In practice
A team says it does Scrum. Its sprints are two weeks, and the last three days of each are testing, so it is running a two-week waterfall. Its daily meeting is fifteen minutes of each person telling the manager what they did, so it is a status report. Its Product Owner is a committee of three department heads who each add items, so nobody is accountable for the order. Its Scrum Master assigns tasks, so the team does not plan its own work. Every event exists and none does what the guide says it is for. The fix is not more ceremony. It is one owner for the backlog, testing inside the work rather than after it, a daily meeting run by the Developers for the Developers, and a Scrum Master who stops assigning and starts removing whatever blocks the team.
Agile is the set of values; Scrum is one framework built to serve them. Running Scrum's events does not make a team agile, and a team can be agile with a different framework or none.
Kanban manages flow continuously with limits on work in progress and no fixed iterations. Scrum works in fixed sprints. Teams combine them, often by running Kanban inside a Scrum sprint, and the two answer different questions about how work should move.
The sprint is Scrum's fixed-length container; Scrum is the whole framework around it. A team that works in two-week cycles without the accountabilities and artefacts has sprints and not Scrum.
Key takeaways
→Three accountabilities, five events, three artefacts, thirteen pages; everything else is an addition.
→The constraints are the content: fixed sprint, fixed goal, one owner, a daily scrum for the Developers.
→The assessments test the guide, which is why experienced practitioners fail them.
Certifications that test this
Vendor exams whose syllabus covers this concept — facts, cost and a preparation path on each page.
A rotating selection from the course directory, drawn from the subcategories where this concept is taught rather than picked for it. Details, price and the provider link are on the course page.
Strategic Planning: Business Strategy using Ancient MappingPlan your business strategy using a world-renowned theory of…
Udemy
FAQ
Is a Scrum Master a project manager?
No. The guide gives the Scrum Master accountability for the framework's effectiveness and none for scope, schedule or assigning work. Organisations that rename their project managers create a role the guide does not describe, and the assessments will mark that answer wrong.
Are story points part of Scrum?
No. They appear nowhere in the guide. They are a widely used estimation practice that many Scrum teams adopt, and many have abandoned in favour of counting items or measuring flow. The framework requires that the Developers size their own work, not how.
Which Scrum certification should I take?
The entry-level assessments from either body prove the vocabulary. Scrum.org's is taken online without a course and never expires; the Scrum Alliance's typically involves a course and periodic renewal. Our Scrum Master and Product Owner pages cover the first.
Sources
The primary text this definition rests on. Read it before you trust ours.
