Agile Scrum Glossary
Agile and Scrum Glossary
Plain-English definitions of the Agile and Scrum terms you will meet when learning Scrum, preparing for a certification or working in an Agile team. Definitions follow the 2020 Scrum Guide where it applies; terms that are popular practice rather than Scrum requirements say so. For structured study, see the Scrum Master Learning Path or All Lessons.
A B C D E I K L M N P S T U V W
A
- Acceptance Criteria
- Specific, testable conditions that a Product Backlog item must meet to be accepted as done from the user's point of view. They clarify scope and are often written as examples or Given/When/Then statements.
- Agile
- A mindset and family of approaches for developing products in short cycles, delivering working results early and often, and adapting to change based on feedback. See What Is Agile?
- Agile Manifesto
- A 2001 statement of four values and twelve principles written by seventeen software practitioners. It prefers individuals and interactions, working software, customer collaboration and responding to change, while still valuing the items on the right. See The Agile Manifesto Explained.
B
- Backlog Refinement
- The ongoing activity of breaking down, clarifying and ordering Product Backlog items so they are ready for future Sprints. The Scrum Guide describes it as an activity rather than a formal event.
- Burndown Chart
- A chart showing the work remaining over time, typically within a Sprint or release. It is a popular tracking tool but is not required by Scrum.
- Burnup Chart
- A chart showing completed work and total scope over time. It makes scope changes visible, which makes it useful for release forecasting.
C
- Certified ScrumMaster (CSM)
- An entry-level certification from Scrum Alliance, usually obtained by attending a course taught by a certified trainer.
- Cycle Time
- The time it takes for a single work item to move from started to finished. Teams use cycle time percentiles to forecast how long similar items will take.
D
- Daily Scrum
- A 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is held at the same time and place every day.
- Definition of Done
- A formal description of the state of an Increment when it meets the quality measures required for the product. Work that does not meet it cannot be released or presented at the Sprint Review. It is one of the three commitments in Scrum.
- Definition of Ready
- A team agreement about what a backlog item should look like before it is pulled into a Sprint. It is a popular practice, not part of the Scrum Guide.
- Developers
- The people in a Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The term includes testers, designers, analysts and others, not only programmers.
E
- Empiricism
- Working from experience and evidence. Scrum is founded on empiricism, built on three pillars: transparency, inspection and adaptation.
- Epic
- A large body of work that can be broken down into smaller Product Backlog items or user stories.
- Extreme Programming (XP)
- An Agile software development approach with engineering practices such as test-driven development, pair programming, continuous integration and refactoring.
I
- Impediment
- Anything that blocks or slows the team's progress toward its Sprint Goal. The Scrum Master helps remove impediments or helps the team do so. See Impediment Management.
- Increment
- A concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments, verified, and meets the Definition of Done. Multiple Increments may be created within a Sprint.
K
- Kanban
- A method for managing flow that visualises work on a board, limits work in progress and manages how work moves through the system. See Kanban for Beginners.
L
- Lead Time
- The total time from when a request is made to when it is delivered, including waiting time before work starts.
- Lean
- A way of thinking, drawn from manufacturing, that focuses on delivering value, eliminating waste and improving flow.
M
- Minimum Viable Product (MVP)
- The smallest version of a product that lets a team learn from real users with the least effort. It is a learning tool, not a low-quality release.
- Monte Carlo Simulation
- A forecasting technique that repeatedly samples a team's historical throughput to produce a range of probable outcomes rather than a single date.
N
- Nexus
- A framework by Scrum.org for scaling Scrum with three to nine Scrum Teams working on one product, using an integration team to manage dependencies.
P
- Planning Poker
- A consensus-based estimation technique in which team members privately choose cards and then discuss differences before re-estimating.
- Product Backlog
- An emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
- Product Goal
- A long-term objective for the Scrum Team, held in the Product Backlog. It is one of the three commitments in Scrum, and the team plans Sprints toward it.
- Product Owner
- The person accountable for maximizing the value of the product resulting from the work of the Scrum Team, including effective Product Backlog management. See Scrum Team Explained.
- Professional Scrum Master (PSM)
- A family of assessments from Scrum.org. PSM I is an online multiple-choice assessment of Scrum Guide knowledge.
S
- Scaled Agile Framework (SAFe)
- A framework for applying Agile practices across many teams in large organisations, using Agile Release Trains and Program Increments.
- Scrum
- A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. It is defined in the Scrum Guide.
- Scrum Guide
- The official definition of Scrum, written and maintained by Ken Schwaber and Jeff Sutherland. The current edition is from 2020.
- Scrum Master
- The person accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness. Scrum Masters are true leaders who serve the Scrum Team and the wider organization.
- Scrum Team
- A small group consisting of one Scrum Master, one Product Owner and Developers. There are no sub-teams or hierarchies inside a Scrum Team.
- Scrum Values
- Commitment, Focus, Openness, Respect and Courage. See The Five Scrum Values in Real Teams.
- Scrumban
- A hybrid that combines Scrum's roles and cadence with Kanban's visual flow and WIP limits.
- Self-managing
- The 2020 Scrum Guide's term for a team that decides internally who does what, when and how, rather than being directed by others.
- Servant Leadership
- A leadership style that focuses on serving the needs of the team and helping people grow, rather than directing from authority.
- Spike
- A time-boxed investigation used to reduce uncertainty, for example to test a technical approach before committing to build it.
- Sprint
- A fixed-length event of one month or less during which an Increment is created. A new Sprint starts immediately after the previous one ends.
- Sprint Backlog
- The Sprint Goal, the Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment. It is owned by the Developers.
- Sprint Goal
- The single objective for the Sprint, created during Sprint Planning. It gives the team flexibility about the work needed to achieve it and is one of the three commitments.
- Sprint Planning
- The event that starts a Sprint and answers why the Sprint is valuable, what can be done, and how the work will be done. It is time-boxed to a maximum of eight hours for a one-month Sprint. See Scrum Events Explained.
- Sprint Retrospective
- The event in which the Scrum Team inspects how the last Sprint went and plans improvements. It is time-boxed to a maximum of three hours for a one-month Sprint.
- Sprint Review
- The event at which the Scrum Team and stakeholders inspect the outcome of the Sprint and determine future adaptations. It is a working session, not a demo-only presentation, time-boxed to a maximum of four hours for a one-month Sprint.
- Stakeholder
- Anyone with an interest in the product, such as users, customers, sponsors and managers, who is not part of the Scrum Team.
- Story Points
- A relative unit of measure teams use to estimate the effort and complexity of backlog items. They are a popular practice, not part of Scrum. See Estimation and Story Points.
T
- Technical Debt
- The accumulated cost of shortcuts and poor design choices that make future change slower and riskier.
- Throughput
- The number of work items a team completes in a given period, such as per Sprint or per week.
- Timebox
- A fixed maximum duration for an activity. All Scrum events are time-boxed.
U
- User Story
- A short description of a feature from the perspective of the person who wants it, often written as: As a [role], I want [goal] so that [benefit].
V
- Velocity
- The amount of work, usually in story points, a team completes in a Sprint. It is useful for forecasting but should not be used to compare teams or as a target. See Scrum Metrics Explained.
- Vertical Slice
- A thin piece of work that cuts through all layers of the system, such as interface, logic and data, to deliver something usable.
W
- Waterfall
- A sequential approach in which requirements, design, build, test and release happen in distinct phases.
- WIP Limit
- A cap on the number of items allowed in a workflow stage at once. It reveals bottlenecks and encourages finishing work before starting new work.
Missing a term or spotted a definition that could be clearer? Tell us on the Contact page.