Glossary
What is Scrum? Roles, events, artefacts
Scrum is a framework with fixed roles, events and artefacts that organises work into sprints. How it fits together — and when it does not fit.
Scrum is a framework that splits work into fixed iterations and defines three roles, several events and three artefacts around them. It prescribes no technique, only a rhythm: plan, work, inspect, adapt.
How it fits together
Roles: product owner (the order of the backlog), scrum master (process and impediments) and the development team. Events: planning, the daily, review and retrospective. Artefacts: product backlog, sprint backlog and increment.
When it does not fit
When work does not fall predictably into timeboxes. Support, operations and anything with unpredictable intake spend planning writing a plan that will not hold — Kanban is more honest there. For teams under three people the scaffolding usually costs more than it returns.
In Zuuna
Sprints, backlog, capacity, planning poker and burndown are all there but optional — the board underneath works without any of those layers.
Related terms
The role that owns the backlog: product owner. The shape requirements take in it: user story.
FAQ
Is Scrum agile?
Scrum is a framework that implements agile principles. A team can follow Scrum to the letter and still not work in an agile way — the ceremonies alone guarantee nothing.
What is Scrumban?
A mixture: sprints and roles from Scrum, flow and WIP limits from Kanban. Common in teams whose intake is partly plannable and partly reactive.