Scrum

Scrum is a lightweight agile framework that helps a small team deliver value in short, fixed-length cycles called sprints, each one month or less. It defines three accountabilities, five events and three artifacts that create a regular rhythm of planning, delivery, inspection and adjustment, so the team can adapt as it learns.

How Scrum Works

Ken Schwaber and Jeff Sutherland developed Scrum in the early 1990s and maintain its official definition, the Scrum Guide, last revised in 2020. The guide describes Scrum as a framework for complex problems, built on empiricism and its three pillars: transparency, inspection and adaptation.

Accountabilities. A Scrum Team is typically 10 or fewer people, with no sub-teams or hierarchies:

• The Product Owner maximizes the value of the product and manages the Product Backlog.
• The Developers create a usable increment each sprint.
• The Scrum Master helps the team and the organization understand and apply Scrum effectively.

Events. The sprint is the container for all other events. Sprints run back to back: a new one starts as soon as the previous one ends. During a sprint, no changes are made that would endanger the Sprint Goal, quality does not decrease, and scope can be clarified and renegotiated with the Product Owner as more is learned. Only the Product Owner can cancel a sprint, and only if its goal becomes obsolete. For a one-month sprint, the guide sets these maximum timeboxes, and shorter sprints usually have shorter events:

Artifacts and commitments. Each artifact has a commitment that gives it focus:

• The Product Backlog, an ordered list of what is needed to improve the product, commits to the Product Goal.
• The Sprint Backlog, the items selected for the sprint plus a plan for delivering them, commits to the Sprint Goal.
• The Increment, a usable step toward the Product Goal, commits to the Definition of Done.

Product Backlog refinement, breaking items down and adding detail until they are small and precise enough to select for a sprint, is an ongoing activity rather than a formal event.

Scrum also names five values: commitment, focus, openness, respect and courage. Many teams add practices the guide does not require, such as user stories, story points and velocity.

Why Scrum Matters

Scrum gives teams a simple structure for working under uncertainty. The sprint creates a predictable rhythm for stakeholders, the Sprint Goal focuses the team, and the review and retrospective build inspection and improvement into every cycle. Because the framework is deliberately incomplete, teams can fit their own practices into it.

The common failure is adopting the events without the empiricism: holding stand-ups and reviews while scope is fixed in advance and feedback changes nothing. For product managers, Scrum's value depends on a well-ordered backlog and a Product Owner with real authority to decide what gets built. Turning goals into sprint-ready tickets with clear scope and acceptance criteria is often where that breaks down.

Scrum Example

A team of six developers, a product owner and a scrum master works in two-week sprints on a field-service app. In Sprint Planning they agree on a Sprint Goal: "Technicians can complete a job report offline." They select the backlog items that support it and plan the work. Each morning they meet for 15 minutes to check progress. At the Sprint Review, a pilot customer tries the offline report and asks for photo attachments, which the product owner adds to the Product Backlog. In the retrospective, the team agrees to test on low-end Android devices earlier.

Scrum vs. Kanban

Scrum works in fixed-length sprints with defined accountabilities and events, and the team commits to a Sprint Goal for each one. Kanban has no fixed iterations or prescribed roles; it manages a continuous flow of work using work-in-progress limits. Teams with plannable feature work often prefer Scrum, while teams with unpredictable incoming work, such as support or operations, often prefer Kanban.