Scrum is the most widely used Agile framework in the world. It gives teams a concrete structure — defined roles, regular events, and specific artifacts — that makes iterative delivery manageable and predictable.
The three Scrum roles
Scrum defines exactly three roles. The Product Owner is accountable for the product backlog — the ordered list of everything the team might build. They decide what goes in, what gets prioritised, and what gets cut. They represent the voice of the customer and the business.
The Scrum Master is the team's process guardian. They're not a project manager — they don't assign tasks or track time. Their job is to ensure the team understands and follows Scrum, to remove impediments that block progress, and to coach the team toward self-organisation. A Scrum Master serves the team, not the other way around.
The Developers (previously called the Development Team) are the people who do the work. In Scrum, 'developers' means anyone who builds the product increment — designers, testers, engineers, writers. The team is cross-functional by design, so all the skills needed to deliver are inside the team, not dependent on external specialists.
The three Scrum artifacts
The Product Backlog is the master list of work — features, fixes, improvements — ordered by value. It's never finished; it evolves as the product and market evolve. The Product Owner owns it.
The Sprint Backlog is the subset of product backlog items the team has committed to completing in the current sprint, plus a plan for how they'll do it. The team owns it, and it's updated daily.
The Increment is the working, usable product output at the end of a sprint. It must meet the team's Definition of Done — a shared agreement about what 'finished' means. Increments are cumulative: each sprint adds to what was built before.
The empirical process
Scrum is built on three pillars: transparency, inspection, and adaptation. Transparency means the team's work, progress, and impediments are visible to everyone. Inspection means the team regularly examines what they've built and how they're working. Adaptation means they change course when inspection reveals a problem.
This empirical loop — make something visible, examine it honestly, adjust — is what makes Scrum work. Without all three pillars, Scrum becomes a set of meetings with no real benefit. Teams that go through the motions of Scrum without genuine transparency and honest inspection get the overhead without the value.
The sprint itself is the heartbeat of this loop. Every sprint produces something real, creates an opportunity to inspect it, and resets the team's direction based on what they learned.
Summary & next steps
Scrum has three roles (Product Owner, Scrum Master, Developers), three artifacts (Product Backlog, Sprint Backlog, Increment), and is built on transparency, inspection, and adaptation. Understanding these building blocks is the foundation for everything else in Agile delivery.
Next you'll walk through the four Scrum events — Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective — and see exactly how they create the rhythm of iterative delivery.