Definition
Scrum
Scrum is an agile framework for delivering work in fixed iterations called sprints. A small cross-functional team plans a sprint, works without mid-sprint scope changes, then inspects and adapts through review and retrospective. Defined roles, events, and artifacts give the framework structure while leaving the actual engineering practices up to the team.
Key takeaways
- Scrum is an agile framework that delivers work in fixed iterations called sprints, governed by three roles, five events, and three artifacts.
- It defines the rhythm of work — planning, standup, review, retrospective — but not the engineering practices a team uses to build.
- Its engine is empiricism: each sprint is a short inspect-and-adapt experiment, so short sprints make a wrong plan cheap.
- The three roles are product owner (priorities), scrum master (process and impediments), and developers (the work).
Scrum is the most widely adopted agile framework. It organizes work into sprints — fixed time-boxes, usually one to four weeks — and prescribes a small set of roles, events, and artifacts to run them. The framework is deliberately lightweight: it tells you how to structure the rhythm of work, not how to design, test, or ship software.
Three roles carry the framework: the product owner owns priorities and the backlog, the scrum master removes impediments and protects the process, and the developers do the work. Five events give it cadence: sprint planning, the daily standup, the sprint itself, the sprint review, and the retrospective. Three artifacts hold the state: the product backlog, the sprint backlog, and the increment.
The engine underneath all of it is empiricism — inspect and adapt. Each sprint is a short experiment: commit to a goal, learn from what shipped, and adjust the plan. Scrum works best when sprints are short enough that a wrong plan is cheap and the team is small enough to coordinate without heavy process.
Planoda supports the full Scrum loop on one schema — backlog, sprint cycles, standups, reviews, and retrospectives — with burndown and velocity charts generated automatically from completion events.
Related terms
- AgileAgile is a family of software-development approaches built on the 2001 Agile Manifesto, which values working software, customer collaboration, and responding to change over rigid plans and documentation. Rather than one process, it is a set of principles — short iterations, continuous feedback, and incremental delivery — that frameworks like Scrum and Kanban put into practice.
- SprintA sprint is a fixed, repeating time-box — usually one to four weeks — during which a Scrum team commits to a focused set of work and aims to ship a usable increment. It is the Scrum term for the iteration other frameworks call a cycle, giving the team a regular cadence for planning, focus, and review.
- Scrum MasterA scrum master is the person accountable for a team's effective use of Scrum. They are a facilitator and coach, not a manager: they run the sprint events, remove impediments blocking the team, shield it from outside disruption, and help the organization adopt agile practices. They have no authority over priorities or who does what work.
- Product OwnerA product owner is the person accountable for maximizing the value a Scrum team delivers. They own and order the product backlog, decide what gets built and in what sequence, and translate stakeholder needs into clear, prioritized work. They are a single, empowered decision-maker — not a committee — so the team always has one authoritative source of priority.
- RetrospectiveA retrospective is a recurring meeting, usually at the end of a cycle, where a team reflects on how it worked — what went well, what didn't, and what to change. Its output is a small set of concrete improvements to try next. The retrospective is the engine of continuous improvement, turning experience into deliberate process change.