Professional Documents
Culture Documents
Menu Login
(https://www.agilealliance.org/)
Agile Glossary
See the practices in context in the Subway Map to Agile Practices (https://www.agilealliance.org/agile101/subway-map-to-agile-
practices/).
Help the Agile community practice continuous learning. If you have suggestions for revisions to existing terms or ideas for new
terms, let us know (https://www.agilealliance.org/agile101/agile-glossary/agile-glossary-feedback/).
A/B/C/D/E/F/G/H/I/K/L/M/N/O/P/Q/R/S/T/U/V
A
Acceptance Test Driven Development (ATDD)
(https://www.agilealliance.org/glossary/atdd/)
Acceptance Test Driven Development (ATDD) involves team members with different perspectives (customer, development,
testing) collaborating to write acceptance tests in advance of implementing the corresponding functionality. (see more)
(https://www.agilealliance.org/glossary/atdd/)
Antipattern (https://www.agilealliance.org/glossary/antipattern/)
https://www.agilealliance.org/agile101/agile-glossary/ 1/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
Antipatterns are common solutions to common problems where the solution is ineffective and may result in undesired Menu Login
consequences. (see more) (https://www.agilealliance.org/glossary/antipattern/)
(https://www.agilealliance.org/)
⇑ back to top
B
Backlog (https://www.agilealliance.org/glossary/backlog/)
See product backlog (https://www.agilealliance.org/glossary/backlog/).
https://www.agilealliance.org/agile101/agile-glossary/ 2/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
(https://www.agilealliance.org/)
C
Collective Ownership (https://www.agilealliance.org/glossary/collective-
ownership/)
Collective code ownership is the explicit convention that every team member can make changes to any code file as necessary:
either to complete a development task, to repair a defect, or to improve the code’s overall structure. (see more)
(https://www.agilealliance.org/glossary/collective-ownership/)
⇑ back to top
D
https://www.agilealliance.org/agile101/agile-glossary/ 3/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
The definition of done is an agreed upon list of the activities deemed necessary to get a product increment, usually represented
by a user story, to a done state by the end of a sprint. (see more) (https://www.agilealliance.org/glossary/definition-of-done/)
⇑ back to top
E
Epic (https://www.agilealliance.org/glossary/epic/)
An epic is a large user story. (see more) (https://www.agilealliance.org/glossary/epic/)
Estimation (https://www.agilealliance.org/glossary/estimation/)
In software development, an “estimate” is the evaluation of the effort necessary to carry out a given development task; this is most
often expressed in terms of duration. (see more) (https://www.agilealliance.org/glossary/estimation/)
https://www.agilealliance.org/agile101/agile-glossary/ 4/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
(https://www.agilealliance.org/)
F
Facilitation (https://www.agilealliance.org/glossary/facilitation/)
A facilitator is a person who chooses or is given the explicit role of conducting a meeting. (see more)
(https://www.agilealliance.org/glossary/facilitation/)
⇑ back to top
G
Given When Then (https://www.agilealliance.org/glossary/gwt/)
The Given-When-Then formula is a template intended to guide the writing of acceptance tests for a User Story: (Given) some
context, (When) some action is carried out, (Then) a particular set of observable consequences should obtain. (see more)
(https://www.agilealliance.org/glossary/gwt/)
⇑ back to top
H
Heartbeat Retrospective
(https://www.agilealliance.org/glossary/heartbeatretro/)
The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify
opportunities for improvement. (see more) (https://www.agilealliance.org/glossary/heartbeatretro/)
⇑ back to top
https://www.agilealliance.org/agile101/agile-glossary/ 5/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
Integration (https://www.agilealliance.org/glossary/integration/)
“Integration” (or “integrating”) refers to any efforts still required for a project team to deliver a product suitable for release as a
functional whole. (see more) (https://www.agilealliance.org/glossary/integration/)
INVEST (https://www.agilealliance.org/glossary/invest/)
The acronym INVEST stands for a set of criteria used to assess the quality of a user story. If the story fails to meet one of these
criteria, the team may want to reword it. (see more) (https://www.agilealliance.org/glossary/invest/)
Iteration (https://www.agilealliance.org/glossary/iteration/)
An iteration is a timebox during which development takes place. The duration may vary from project to project and is usually
fixed. (see more) (https://www.agilealliance.org/glossary/iteration/)
⇑ back to top
K
Kanban (https://www.agilealliance.org/glossary/kanban/)
https://www.agilealliance.org/agile101/agile-glossary/ 6/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
The Kanban Method is a means to design, manage and improve flow for knowledge work and allows teams to start where they Menu Login
are to drive evolutionary change. (see more) (https://www.agilealliance.org/glossary/kanban/)
(https://www.agilealliance.org/)
⇑ back to top
L
Lead Time (https://www.agilealliance.org/glossary/lead-time/)
Lead Time is the time between a customer order and delivery. In software development, it can also be the time between a
requirement made and its fulfillment. (see more) (https://www.agilealliance.org/glossary/lead-time/)
⇑ back to top
M
Milestone Retrospective (https://www.agilealliance.org/glossary/milestone-
retrospective/)
A Milestone Retrospective is a team’s detailed analysis of the project’s significant events after a set period of time or at the
project’s end. (see more) (https://www.agilealliance.org/glossary/milestone-retrospective/)
https://www.agilealliance.org/agile101/agile-glossary/ 7/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
⇑ back to top
N
Niko-niko Calendar (https://www.agilealliance.org/glossary/nikoniko/)
A Niko-niko Calendar is updated daily with each team member’s mood for that day. Over time the calendar reveals patterns of
change in the moods of the team, or of individual members. (see more) (https://www.agilealliance.org/glossary/nikoniko/)
⇑ back to top
O
Open Space (https://www.agilealliance.org/glossary/open-space/)
In Open Space meetings, events, or conferences, participants create and manage their own agenda of parallel sessions around a
specific theme. (see more) (https://www.agilealliance.org/glossary/open-space/)
⇑ back to top
P
Pair Programming (https://www.agilealliance.org/glossary/pairing/)
Pair programming consists of two programmers sharing a single workstation (one screen, keyboard and mouse among the pair).
(see more) (https://www.agilealliance.org/glossary/pairing/)
Personas (https://www.agilealliance.org/glossary/personas/)
https://www.agilealliance.org/agile101/agile-glossary/ 8/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
Personas are synthetic biographies of fictitious users of the future product. (see more) Menu Login
(https://www.agilealliance.org/glossary/personas/)
(https://www.agilealliance.org/)
⇑ back to top
Q
Quick Design Session (https://www.agilealliance.org/glossary/quickdesign/)
When “simple design” choices have far-reaching consequences, two or more developers meet for a quick design session at a
whiteboard. (see more) (https://www.agilealliance.org/glossary/quickdesign/)
⇑ back to top
R
https://www.agilealliance.org/agile101/agile-glossary/ 9/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
Relative estimation consists of estimating tasks or user stories by comparison or by grouping of items of equivalent difficulty. (see
more) (https://www.agilealliance.org/glossary/relative-estimation/)
⇑ back to top
S
Scrum (https://www.agilealliance.org/glossary/scrum/)
Scrum is a process framework used to manage product development and other knowledge work. (see more)
(https://www.agilealliance.org/glossary/scrum/)
https://www.agilealliance.org/agile101/agile-glossary/ 10/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
A team adopting the “simple design” practice bases its software design strategy on a set of “simple design” principles. (see more) Menu Login
(https://www.agilealliance.org/glossary/simple-design/)
(https://www.agilealliance.org/)
⇑ back to top
T
Task Board (https://www.agilealliance.org/glossary/taskboard/)
The most basic form of a task board is divided into three columns labeled “To Do,” “In Progress,” and “Done.” Cards are placed in
the columns to reflect the current status of that task. (see more) (https://www.agilealliance.org/glossary/taskboard/)
https://www.agilealliance.org/agile101/agile-glossary/ 11/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
The team (ideally the whole team, including the product owner or domain expert) has the use of a dedicated space for the
duration of the project, set apart from other groups’ activities. (see more) (https://www.agilealliance.org/glossary/team-room/)
Timebox (https://www.agilealliance.org/glossary/timebox/)
A timebox is a previously agreed period of time during which a person or a team works steadily towards completion of some
goal. (see more) (https://www.agilealliance.org/glossary/timebox/)
⇑ back to top
U
Ubiquitous Language (https://www.agilealliance.org/glossary/ubiquitous-
language/)
Striving to use the vocabulary of a given business domain, not only in discussions about the requirements for a software product,
but in discussions of design as well and all the way into “the product’s source code itself.” (see more)
(https://www.agilealliance.org/glossary/ubiquitous-language/)
https://www.agilealliance.org/agile101/agile-glossary/ 12/16
6/1/2021 Agile Glossary and Terminology | Agile Alliance
Usability testing is an empirical, exploratory technique to answer questions such as “how would an end user respond to our
software under realistic conditions?” (see more) (https://www.agilealliance.org/glossary/usability/)
⇑ back to top
V
Velocity (https://www.agilealliance.org/glossary/velocity/)
At the end of each iteration, the team adds up effort estimates associated with user stories that were completed during that
iteration. This total is called velocity. (see more) (https://www.agilealliance.org/glossary/velocity/)
⇑ back to top
https://www.agilealliance.org/agile101/agile-glossary/ 13/16