OneMorePoint

Agile & Scrum Glossary

Free tool

Scrum roles

Product Owner
The person accountable for maximizing the value of the product, primarily by managing the Product Backlog - what gets built and in what order.
Scrum Master
Accountable for establishing Scrum as defined in the Scrum Guide, coaching the team, and removing impediments to the team's progress. Not a project manager or a people manager.
Developers
The people on the Scrum Team committed to creating a usable Increment each Sprint - the term covers anyone doing the work, not only software engineers.
Scrum Team
The Product Owner, Scrum Master, and Developers together - a small, cross-functional, self-managing team with no sub-teams or hierarchies.
Stakeholder
Someone outside the Scrum Team with an interest in the product's outcome - a customer, sponsor, or user - who provides input, especially at Sprint Review.

Scrum events

Sprint
A fixed-length timebox, one month or less, during which a usable Increment is created. Sprints happen back-to-back with no gap.
Sprint Planning
The event that kicks off a Sprint: the team decides what can be delivered and how the work will be achieved, producing a Sprint Goal.
Daily Scrum
A 15-minute daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
Sprint Review
An inspection of the Sprint's outcome with stakeholders, held at the end of the Sprint, to determine future adaptations - not a formal sign-off gate.
Sprint Retrospective
The final event of a Sprint, where the team inspects how the last Sprint went (people, process, tools) and plans improvements for the next one.
Backlog Refinement
The ongoing activity of adding detail, estimates, and order to Product Backlog items - not a formal Scrum event with a fixed timebox, but ongoing work.

Scrum artifacts

Product Backlog
The single, ordered, ever-evolving list of everything known to be needed in the product - the Product Owner's primary tool.
Sprint Backlog
The Sprint Goal, the Product Backlog items selected for the Sprint, and the plan for delivering them - owned entirely by the Developers.
Increment
A concrete, usable step toward the product goal - every Increment must meet the Definition of Done and be additive to prior Increments.
Sprint Goal
The single objective for the Sprint - the commitment that gives the Sprint Backlog coherence, not a list of the tickets in it.
Definition of Done
A shared, formal description of the quality standard every Increment must meet - once met, work is genuinely releasable.
Definition of Ready
A team's own agreed bar a backlog item clears before entering a Sprint - not part of the official Scrum Guide, but a common team-level practice.
Product Goal
The long-term objective for the Scrum Team - the Product Backlog exists to serve this single goal, and Sprint Goals are steps toward it.

Estimation

Story Point
A relative, team-calibrated unit for sizing backlog items - not a fixed conversion to hours, and not comparable across teams.
Velocity
The average amount of Product Backlog turned into a usable Increment per Sprint, typically measured in story points - a planning input, not a productivity score.
Planning Poker (Scrum Poker)
A consensus estimation technique: each estimator privately picks a card, all reveal simultaneously, and the team discusses any disagreement before settling on a number.
Fibonacci Sequence (agile)
The modified scale 0, 1, 2, 3, 5, 8, 13, 21 used for story points - the widening gaps match how estimation uncertainty grows with size.
T-Shirt Sizing
A coarse relative-estimation technique using XS-XXL instead of numbers, trading precision for speed - common for roadmap-level sizing.
Affinity Estimation
Silently sorting backlog items along a size spectrum without discussion, then reviewing the result - a fast way to size a large batch.
Three-Point (PERT) Estimation
Combining optimistic, most-likely, and pessimistic values into a weighted expected value: (O + 4M + P) / 6 - produces a confidence range, not a consensus.
Wideband Delphi
A structured group-estimation method (independent estimate, anonymized comparison, discussion, re-estimate) - the historical ancestor of Planning Poker.
Dot Voting
A prioritization technique, not estimation - participants distribute a fixed number of votes across options to surface what matters most.
Cone of Uncertainty
The principle that estimate accuracy improves as a project moves from a vague idea toward completion - early estimates can be off by 4x in either direction.
Anchoring Bias
The tendency for an estimate to drift toward the first number mentioned, even an arbitrary one - the reason hidden, simultaneous voting exists.

Kanban

Kanban Board
A visual board with columns representing workflow states, used to make work and its flow visible.
WIP Limit
A cap on how many items can be in progress in a given workflow state at once - the core mechanism Kanban uses to expose bottlenecks.
Pull System
Work is pulled into the next stage only when capacity exists, rather than pushed in on a schedule - contrasts with Scrum's batch-planned Sprint.
Cycle Time
The elapsed time from when work starts on an item to when it finishes - a core Kanban flow metric.
Lead Time
The elapsed time from when a request is made to when it is delivered - includes time waiting before work starts, unlike cycle time.
Scrumban
A hybrid combining Scrum's planning cadence and retrospectives with Kanban's continuous flow and WIP limits.

Metrics & general terms

Burndown Chart
A chart plotting remaining work against an ideal pace toward zero across a Sprint - shows whether a Sprint is on track.
Burnup Chart
A chart plotting completed work and total scope as two separate lines - unlike a burndown, it shows scope changes directly.
Technical Debt
The implied cost of future rework caused by choosing an expedient solution now instead of a better one that would take longer.
Spike
A timeboxed investigation used to answer a specific question or reduce uncertainty enough to estimate the real work - not a story with a point value.
INVEST
A checklist for a well-formed user story: Independent, Negotiable, Valuable, Estimable, Small, Testable.
User Story
A short description of a feature from a user's perspective, typically "As a [role], I want [goal], so that [benefit]."
Epic
A large body of work too big to fit in one Sprint, broken down into smaller stories before it becomes sprint-ready.
Acceptance Criteria
The specific, testable conditions a story must satisfy to be considered complete - often written as Given/When/Then scenarios.
RICE Score
A prioritization framework: (Reach x Impact x Confidence) / Effort, used to compare product bets on a shared scale.
WSJF (Weighted Shortest Job First)
A SAFe prioritization formula: Cost of Delay divided by Job Size, favoring high-value, quick jobs over slow ones of equal value.
MVP (Minimum Viable Product)
The smallest version of a product that delivers enough value to test a hypothesis with real users or customers.

About this glossary

Every term below is written to be accurate on its own, not just long - a curated set of the terms that actually come up in Scrum, Kanban, and estimation work, not a padded list chasing a round number. Search to filter, or scan by category.

Where to go deeper

This glossary defines terms; the linked guides explain the reasoning behind them in full - the complete Scrum Poker guide, story points, and agile estimation techniques are the best starting points if a definition here leaves you wanting the full picture.

Frequently asked questions

It is curated for accuracy, not padded to a round number - every definition is written to be correct on its own rather than filler chasing a term count.