Scrum Handbook

Overview

Scrum is an Agile framework for developing and sustaining complex products. It uses time-boxed iterations called Sprints (1–4 weeks) to deliver working software incrementally.

Type Framework Iteration Sprint (1–4 weeks) Team Size 3–9 developers

Scrum Roles

Product Owner — owns the Product Backlog, prioritizes features, represents stakeholders
Scrum Master — facilitates Scrum events, removes impediments, coaches the team
Development Team — self-organizing, cross-functional, delivers the increment

Scrum Events

Event	Purpose	Duration
Sprint	Time-boxed iteration to deliver a "Done" increment	1–4 weeks
Sprint Planning	Team selects backlog items and plans the Sprint	≤ 8 hrs (4-week sprint)
Daily Scrum	15-min sync — what did I do, what will I do, any blockers?	15 minutes
Sprint Review	Demo working software to stakeholders	≤ 4 hrs
Sprint Retrospective	Inspect and adapt team process	≤ 3 hrs

Scrum Artifacts

Product Backlog — ordered list of all desired work (User Stories, Epics, Tasks)
Sprint Backlog — subset of Product Backlog selected for the Sprint + plan
Increment — sum of all completed backlog items — must be "Done"
Burndown Chart — tracks remaining work over Sprint timeline

Common Interview Topics

Scrum vs Kanban differences
How to handle a team member missing the Daily Scrum
Definition of Done criteria
How to split large Epics into Stories
Velocity calculation and forecasting
Scrum of Scrums for scaling