Scrum is an agile framework for managing software development with defined roles, events, and artifacts. A cross-functional team works in sprints (1-4 weeks) to deliver increments of working software. Scrum is the most widely used agile framework, adopted by over 80% of agile teams.

How Scrum Works

Sprint cycle: Sprint Planning (what to build) → Daily Scrums (15-min standups) → Development work → Sprint Review (demo to stakeholders) → Retrospective (process improvement). The Product Owner prioritizes the backlog; the Scrum Master removes blockers; the team self-organizes to deliver.

Key Concepts

  • Product Owner — Owns the backlog — prioritizes features, defines acceptance criteria, represents stakeholder needs
  • Scrum Master — Facilitates scrum events, removes impediments, coaches the team on scrum practices
  • Sprint — A time-boxed iteration (usually 2 weeks) with a defined sprint goal
  • Sprint Board — Visual representation of work: To Do → In Progress → Done

Frequently Asked Questions

Scrum vs Kanban?

Scrum uses fixed sprints with planned scope. Kanban uses continuous flow with WIP (work-in-progress) limits. Scrum for predictable cadence; Kanban for continuous delivery with variable workload.