Scrum fundamentals: roles, events, and artifacts

The entire Scrum Guide is a short document — three roles, five events, three artifacts, and the rules connecting them. It deliberately says very little about how to build software (no prescribed engineering practices, no mandated tooling) and a lot about the rhythm and accountability structure a team operates inside. That minimalism is the point: Scrum is meant to expose problems (a team that can't estimate, a stakeholder who won't commit to priorities, a codebase too fragile to change safely) rather than solve them for you.

The common failure mode here isn't a missing role — it's role bleed: a Product Owner who dictates how the team should implement something, or a Scrum Master who acts as a manager assigning individual tasks. Both erode the self-organization Scrum is built around.

Each event has one job — Planning decides what and how, the Daily Scrum re-plans the next day, Review inspects the product, Retrospective inspects the process. Conflating them (turning the Daily Scrum into a status-report meeting, or Sprint Review into an internal demo with no real stakeholders present to give feedback) is where teams start going through the motions without getting the actual value each event exists to provide — the specific ways this happens get their own dedicated lessons later in this domain.

Each artifact has an associated commitment that keeps it honest, rather than just being a list: the Product Backlog's commitment is the Product Goal (the longer-term objective it's steering toward), the Sprint Backlog's is the Sprint Goal (the single coherent objective this sprint exists to achieve, not just an unordered pile of tickets), and the Increment's is the Definition of Done (the shared, objective standard for "actually finished" — covered in its own lesson later in this domain). Without these, the artifacts degrade into disconnected lists — a backlog with no direction, a sprint with no unifying purpose, an increment with an ambiguous, team-by-team definition of "done."