Scrum¶

Scrum is the most widely used agile methodology. It is a lightweight framework: it prescribes a small set of roles, events and artifacts, and deliberately says nothing about engineering practices, which come from XP or from the team itself.

Everything in Scrum exists to shorten the loop between deciding to build something and learning whether it was the right thing.

The framework at a glance¶

Element	Items
Roles	Product Owner, Scrum Master, Developers
Events	Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
Artifacts	Product Backlog, Sprint Backlog, Increment
Commitments	Product Goal, Sprint Goal, Definition of Done

graph LR
    PB[Product Backlog] -->|Sprint Planning| SB[Sprint Backlog]
    SB --> S[Sprint: daily work + Daily Scrum]
    S --> I[Increment]
    I -->|Sprint Review| PB
    S -->|Retrospective| S

Artifacts¶

Product Backlog, the single ordered list of everything that might be built. Owned by the Product Owner, never "final", refined continuously.
Sprint Backlog, the items pulled for this Sprint plus the plan to deliver them. Owned by the Developers.
Increment, the sum of completed items, meeting the Definition of Done and therefore potentially shippable.

The Definition of Done is the quality gate. Without a shared, strict one, "done" drifts and the Increment silently accumulates technical debt.

Pages in this section¶

Scrum Principles, the ideas the framework rests on.
Roles in Scrum, who is accountable for what.
Sprints, the timebox that contains everything else.
Scrum Events, the five events and what each inspects.
Scrum Artifacts, the backlogs, the Increment and their commitments.
Definition of Done, the quality gate that makes "done" mean something.

Check Your Understanding¶

#

Who owns the Sprint Backlog?

#

What makes an Increment "potentially shippable"?

Assessment¶

Work through the Scrum assessment once you have read this section.