Lesson 2.3 — The whole picture: one Sprint end to end

Before zooming in on each part, it helps to see the whole Scrum system at once. Scrum has three accountabilities (the people), five events (the meetings), and three artifacts (the work products). The three accountabilities are: the Product Owner, who maximises product value and owns the ordered Product Backlog; the Scrum Master, a true leader who serves the team — not a boss or task dispatcher — and helps establish Scrum; and the Developers, who create a usable Increment each Sprint. Together they form a small, cross-functional, self-managing Scrum Team, typically ten or fewer people. Each Sprint is a fixed-length container of one month or less. Inside a Sprint, four events nest: Sprint Planning kicks off the Sprint (the team selects work and crafts a Sprint Goal); the Daily Scrum is a 15-minute event held every day for Developers to inspect progress toward the Sprint Goal; the Sprint Review happens at the end to inspect the Increment with stakeholders and adapt the Product Backlog; the Sprint Retrospective closes the Sprint — the team inspects how they worked and plans improvements for the next Sprint. Then the next Sprint begins immediately. The three artifacts carry the work and its commitments: the Product Backlog (commitment: Product Goal) holds everything that might be done; the Sprint Backlog (commitment: Sprint Goal) is the plan for the Sprint; the Increment (commitment: Definition of Done) is the sum of all completed work. Trace a Sprint: the team plans → builds and syncs daily → reviews the Increment with stakeholders → reflects on the process → and repeats. Every loop adds inspected, adapted value.