Agile glossary

Agile software development is not one single methodology — it is a category that includes many different methodologies and frameworks. These include kanban, scrum, lean, and others. What do all of these methodologies have in common? A commitment to adaptive planning, iterative development, and continuous improvement.

This dictionary provides a list of definitions of agile-related keywords to help you better understand agile terms and methodologies.


Acceptance criteria

Requirements that must be met for a specific item in the product backlog to be considered complete. Acceptance criteria is helpful for estimating time and resources needed during sprint planning. Note that although they seem similar, acceptance criteria is different from definition of ready (DoR).

Acceptance testing

The fourth stage of software testing when developers validate that the software addresses user needs and problems. (See also: unit testing, integration testing, system testing.)

Agile software development

A collection of software development methodologies and frameworks that promote an iterative approach and continuous delivery. Agile teams work in short increments with frequent release cycles.


A scrum term representing items that represent work to be done in order to deliver value against the product goal. Scrum artifacts include the product backlog, the sprint backlog, and increments.



A list of work items. In scrum there are two backlogs: the product backlog and the sprint backlog.

Backlog refinement

Process of adding detail and estimates to items in a backlog. During backlog refinement (or “backlog grooming”), large items may be broken down into smaller units.

Burndown chart

A visual graphic showing work against time allowed. Burndown charts are a reporting tool used by scrum teams to understand progress within a sprint.

Burnup chart

A visual graphic showing the amount of work that has been completed during a sprint. Burnup charts are used by scrum teams to track progress toward a sprint goal and ensure work falls within the sprint's scope.



A measurement of the amount of work that can be completed during a sprint. Capacity is based on the number of hours an individual or a team has available to complete work during a given sprint.

Continuous delivery

A DevOps practice that helps teams keep code in a deployable state by automating processes to build, test, and deploy code to an acceptance environment.

Continuous deployment

A DevOps practice that represents end-to-end automation of building, testing, staging, and code deployment processes.

Continuous everything

A DevOps principle that helps teams increase agility through automating testing, staging, and deployment processes. It encompasses the practices of continuous integration, continuous delivery, and continuous deployment.

Continuous integration

A DevOps practice that helps teams automate, build, and test processes so they always have code ready for deployment.


Daily standup

One of the five scrum events, this is a quick meeting with the scrum team to review the day’s work, assess progress, and capture any roadblocks.

Definition of done (DoD)

An organization's formal definition of when an increment of work meets the quality measures required for release.

Definition of ready (DoR)

An organization’s formal definition of quality. Once an item reaches DoR it becomes an increment.


An event, collaboration, or piece of work that relies on involvement from another team(s). Dependencies must be completed in order for an agile team to finish a sprint item.


Engineers who complete work during a sprint. Developers, who typically work in groups of three to nine people, are responsible for all aspects of delivering a working and tested increment.


An approach to software delivery that promotes deep collaboration between development and operations. DevOps focuses on automation and a shortened systems development life cycle (SDLC).



A large body of work that describes major areas of functionality. An epic is typically delivered across multiple releases.


A prediction made by the scrum team about the amount of effort it will take to complete an increment of work, often measured in user story points or time.



A scrum artifact that defines the value that will be delivered to customers upon completion of a sprint. Increments typically build on each other and are stepping stones to delivering a Complete Product Experience (CPE).

Integration testing

The second stage of software testing when developers confirm that units are working together to produce the expected result. (See also: unit testing, system testing, acceptance testing.)



A pull system used by agile teams to visualize work. Work is only pulled when there is demand for it and team members only pull work when they have the capacity to complete the task.

Kanban board

A visual tool to track work as it moves through the development process. Kanban boards often organize work by status — such as not started, in progress, in review, and done.


Lean software development

An agile framework with roots in manufacturing that promotes optimizing workflows by reducing wasted time and resources.


Product backlog

A prioritized inventory of features, defects, prioritized ideas, or technical work that has yet to be worked on. The product backlog should include work that is considered valuable from the product owner’s perspective.

Product manager

Product managers are outwardly focused on the market, customers, positioning, and pricing. They are responsible for setting vision, goals, and major initiatives for the product. They do high-level product planning and own the product roadmap.

Product owner

Product owners are inwardly focused. They influence the product manager’s responsibilities, such as release planning and feature definition. They represent the customer and advocate for the business case on the scrum team. They are the only member of the team who can change the order of features in the product backlog and choose whether to release a sprint.


Scaled Agile Framework®

The Scaled Agile Framework® (SAFe®) is a set of guidelines for implementing agile and lean principles at scale. SAFe® includes its own set of core principles and guidance for action across three main levels of an organization: team, program, and portfolio.

Scrum board

This is where the sprint happens. A scrum board is a visualization of all of the work in an ongoing sprint. Items are typically displayed across different workflow stages, which helps teams stay organized, assign work, and track progress.

Scrum of scrums

A time-boxed meeting designed to coordinate the work of multiple scrum teams working on the same project — integrating outputs and eliminating any impediments.

Scrum master

The scrum team member who helps the development team stay on task, maintain alignment with scrum techniques, and eliminate roadblocks. Scrum masters play the role of coach and motivator — not enforcer.


An agile methodology that combines elements of scrum with elements of kanban. Scrumban teams blend the structure provided by scrum with the flexibility and workflow visualization of kanban.


Originating from Extreme Programming, a spike is a type of user story or feature that is created to dedicate time to research. Instead of producing shippable work, a spike is focused on finding answers to problems and gathering necessary information for upcoming work.


A time-boxed iteration of work that typically lasts between one and four weeks. A sprint includes defined features or user stories to complete with the goal of delivering usable functionality to customers.

Sprint backlog

A list of upcoming work to be completed in a sprint — in the form of user stories — that is often displayed on the scrum board. The sprint backlog fills up when the engineering team and the product owner work together to divvy up planned releases into sprint cycles.

Sprint goal

The stated objective of a sprint. Sprint goals help development teams align on priorities and understand why they are building the current increment.

Sprint planning

The planning meeting at the start of each sprint. The product owner, scrum master, and development team meet to determine the set of items from the backlog that will be completed during the sprint.

Sprint retrospective

A separate meeting from the sprint review where the team discusses what went well and what did not go as planned during the sprint. The goal of a retrospective is to identify opportunities for future improvement.

Sprint review

A review meeting that happens after the sprint is complete. The development team typically gives a demo to show what they accomplished, and stakeholders provide feedback to help the product owner decide if the sprint's objective has been reached.

Story points

A unit of measurement used to estimate the amount of effort necessary to complete a development task. The number of story points assigned to a user story is based on factors like the volume of work, complexity, and risk.

System testing

The third stage of software testing when developers ensure code can run in the environment where it will be deployed. (See also: unit testing, integration testing, and acceptance testing.)


Technical debt

A measurement of system maintenance costs that result from choosing a limited short-term solution over a higher quality solution that requires more time and resources. Technical debt refers to the overhead of maintaining and eventually reworking such a system.


A strategic initiative that describes high-level direction and connects development work to overall goals.


Unit testing

The first stage of software testing when developers verify that code is working correctly at its most foundational level. Unit testing includes testing each unit against possible scenarios that end users might encounter while using the software. (See also: integration testing, system testing, and acceptance testing.)

User story

A product function that delivers new value for customers. User stories are written from the user's perspective following this formula: As a [type of user], I want to [perform some task] so that I can [achieve some goal].



A metric for determining how much work a team can accomplish during a sprint. On a basic level, velocity is calculated by adding up the completed user story points at the end of a sprint.


Work in progress (WIP)

In scrum, WIP refers to the total number of work increments that the engineering team is currently working on. Scrum teams may set WIP limits to focus on fewer tasks at a given time.

A great agile development team needs the right tools. Try Aha! Develop free for 30 days.