The complete Scrum guide: accountabilities, events, artifacts and principles
Quick summary: the structure of Scrum
Scrum defines three accountabilities (Product Owner, Scrum Master and Developers), five events (the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective) and three artifacts (Product Backlog, Sprint Backlog and Increment).
Each artifact carries a commitment — the Product Goal, the Sprint Goal and the Definition of Done — that gives it transparency and focus.
Five values sustain the framework in practice: commitment, focus, openness, respect and courage.
Before diving into reading:
This guide walks through every element the framework defines and why it exists. It is a deeper companion to the introduction to Scrum.
Keep one idea in mind throughout: every piece of Scrum exists to strengthen transparency, inspection or adaptation. When you understand what each element protects, adapting Scrum to your context becomes much safer.
1) The Scrum Team
The Scrum Team is a small, cohesive unit — typically ten or fewer people — with no sub-teams and no hierarchies inside it. It contains one Product Owner, one Scrum Master and Developers, and it is cross-functional: together, its members have all the skills needed to create value each Sprint.
The team is self-managing: it decides internally who does what, when and how. Accountability for the increment belongs to the whole team, not to individuals.
2) Product Owner
The Product Owner is accountable for maximizing the value of the product. In practice this means developing and communicating the Product Goal, creating and ordering Product Backlog items and making sure the backlog is transparent and understood.
The Product Owner is one person, not a committee. Others can influence priorities, but changes go through the Product Owner — which protects the team from contradictory demands.
3) Scrum Master
The Scrum Master is accountable for Scrum being understood and effective. They coach the team in self-management, help remove impediments, keep events productive and within their time-boxes, and help the Product Owner with backlog techniques.
The Scrum Master also serves the organization: helping stakeholders understand empirical work and removing barriers between them and the team. It is a leadership role based on service, not command.
4) Developers
Developers are the people who create the increment, whatever their specialty — code, design, testing, writing or analysis. They plan the Sprint Backlog, adapt it daily, hold each other accountable and instill quality through the Definition of Done.
Scrum deliberately uses one name for all of them. Skills differ, but accountability for delivering a Done increment is shared.
5) The five events
The Sprint is the container for all other events, with a fixed length of one month or less. Sprint Planning answers three questions: why is this Sprint valuable (the Sprint Goal), what can be Done, and how will the work get done.
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the day's plan. The Sprint Review inspects the increment with stakeholders and adapts the Product Backlog. The Sprint Retrospective inspects the process — people, interactions, tools and the Definition of Done — and selects improvements for the next Sprint.
- Sprint: one month or less, no gaps between Sprints.
- Sprint Planning: maximum 8 hours for a one-month Sprint.
- Daily Scrum: 15 minutes, same time and place every day.
- Sprint Review: maximum 4 hours for a one-month Sprint.
- Sprint Retrospective: maximum 3 hours for a one-month Sprint.
6) The three artifacts and their commitments
The Product Backlog is the single, ordered list of everything that might improve the product; its commitment is the Product Goal, a long-term objective. The Sprint Backlog is the plan for the current Sprint — the Sprint Goal, the selected items and the plan to deliver them. The Increment is the sum of completed work that meets the Definition of Done.
The commitments make each artifact measurable: the Product Goal tells you where the backlog is heading, the Sprint Goal tells you why the Sprint matters, and the Definition of Done tells you what quality means. Work that does not meet the Definition of Done returns to the Product Backlog — it is not part of the increment.
None of the artifacts is a board, and Scrum does not prescribe one. Most teams add a visual board as a complementary technique to make the Sprint Backlog transparent — see the Scrum board article for a practical setup.
7) Scrum values and principles
Five values make the framework work: commitment to the goals, focus on the Sprint, openness about the work and its challenges, respect among team members, and courage to do the right thing and tackle hard problems.
These are not decoration. Transparency requires openness and courage; self-management requires respect and commitment; and short cycles only pay off with focus. Teams that struggle with Scrum usually struggle with a value, not with an event.
8) Conclusion
Scrum is a compact system: three accountabilities, five events, three artifacts, three commitments and five values. Each element protects the empirical loop of transparency, inspection and adaptation.
Use this guide as a reference when adapting the framework: change what you like around Scrum, but if you remove an element, know which pillar you are weakening. The official Scrum Guide remains the definitive source.