See the practices in context in the 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.

A / B / C / D / E / F / G / H / IK / L / M / N / P / Q / R / S / T / U / V

A

Acceptance Test Driven Development (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)

Acceptance Testing

An acceptance test is a formal description of the behavior of a software product, generally expressed as an example or a usage scenario. A number of different notations and approaches have been proposed for such examples or scenarios. In many cases the aim is that it should be possible to automate the execution of such tests by a software tool, either ad-hoc to the development team or off the shelf. (see more)

Antipattern

Antipatterns are common solutions to common problems where the solution is ineffective and may result in undesired consequences. (see more)

Automated Build

In the context of software development, build refers to the process that converts files and other assets under the developers' responsibility into a software product in its final or consumable form. The build is automated when these steps are repeatable, require no direct human intervention, and can be performed at any time with no information other than what is stored in the source code control repository. (see more)

B

Backlog

A backlog is an ordered list of items representing everything that may be needed to deliver a specific outcome.  There are different types of backlogs depending on the type of item they contain and the approach being used. (see more)

Backlog Grooming

Backlog grooming is when the product owner and some, or all, of the rest of the team refine the backlog on a regular basis to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery. (see more)

Behavior Driven Development (BDD)

BDD is a practice where members of the team discuss the expected behavior of a system in order to build a shared understanding of expected functionality. (see more)

Burndown Chart

Burndown charts and burnup charts track the amount of output (in terms of hours, story points, or backlog items) a team has completed across an iteration or a project. (see more)

Business Agility

Business agility is the ability of an organization to sense changes internally or externally and respond accordingly in order to deliver value to its customers. (see more)

C

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)

Continuous Deployment

Continuous deployment aims to reduce the time elapsed between writing a line of code and making that code available to users in production. To achieve continuous deployment, the team relies on infrastructure that automates and instruments the various steps leading up to deployment, so that after each integration successfully meeting these release criteria, the live application is updated with new code. (see more)

Continuous Integration

Continuous Integration is the practice of merging code changes into a shared repository several times a day in order to release a product version at any moment. This requires an integration procedure which is reproducible and automated. (see more)

CRC Cards

Class Responsibility Collaborator (CRC) Cards are an object oriented design technique teams can use to discuss what a class should know and do and what other classes it interacts with. (see more)

Customer Development

Customer development is a four-step framework that provides a way to use a scientific approach to validate assumptions about your product and business. (learn more)

D

Daily Meeting

The daily meeting is one of the most commonly practiced Agile techniques and presents opportunity for a team to get together on a regular basis to coordinate their activities. (see more)

Definition of Done

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)

Definition of Ready

Definition of Ready involves creating clear criteria that a user story must meet before being accepted into an upcoming iteration. This is typically based on the INVEST matrix. (see more)

E

Epic

An epic is a large user story. (see more)

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)

Exploratory Testing 

Exploratory testing is, more than strictly speaking a "practice," a style or approach to testing software which is often contrasted to "scripted testing." (see more)

Extreme Programming

Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team. XP is the most specific of the agile frameworks regarding appropriate engineering practices for software development. (see more)

F

Facilitation

A facilitator is a person who chooses or is given the explicit role of conducting a meeting. (see more)

Frequent Releases

An Agile team frequently releases its product into the hands of end users, listening to feedback, whether critical or appreciative. (see more)

G

Given When Then

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)

H

Heartbeat Retrospective

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)

I

Incremental Development

In an Agile context, Incremental Development is when each successive version of a product is usable, and each builds upon the previous version by adding user-visible functionality.  (see more)

Information Radiators

"Information radiator" is the term for any of a number of visual displays which a team places in a highly visible location, so that all team members can see the latest information at a glance. (see more)

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)

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)

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)

Iterative Development

Agile projects are iterative insofar as they intentionally allow for "repeating" software development activities, and for potentially "revisiting" the same work products (the phrase "planned rework" is sometimes used; refactoring is a good example). (see more)

K

Kanban

The Kanban Method is a means to design, manage and improve flow for knowledge work and allows teams to start where they are to drive evolutionary change. (see more)

Kanban Board

A Kanban Board is a visual workflow tool consisting of multiple columns. Each column represents a different stage in the workflow process. (see more)

L

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)

M

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)

Minimum Marketable Feature (MMF)

A Minimum Marketable Feature is a small, self-contained feature that can be developed quickly and that delivers significant value to the user. (see more)

Minimum Viable Product (MVP)

A Minimum Viable Product is, as Eric Ries said, the "version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort." (see more)

Mob Programming

Mob Programming is a software development approach where the whole team  works on the same thing, at the same time, in the same space, and at the same computer. (see more)

Mock Objects

Mock Objects (commonly used in the context of crafting automated unit tests) consist of instantiating a test-specific version of a software component. (see more)

N

Niko-niko Calendar

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)

P

Pair Programming

Pair programming consists of two programmers sharing a single workstation (one screen, keyboard and mouse among the pair).  (see more)

Personas

Personas are synthetic biographies of fictitious users of the future product. (see more)

Planning Poker

An approach to estimation used by Agile teams. Each team member "plays" a card bearing a numerical value corresponding to a point estimation for a user story. (see more)

Points (estimates in) 

Agile teams generally prefer to express estimates in units other than the time-honored "man-hours." Possibly the most widespread unit is "story points." (see more)

Product Owner

The product owner is a role created by the Scrum Framework responsible for making sure the team delivers the desired outcome. (see more)

Project Chartering

A high-level summary of the project's key success factors displayed on one wall of the team room as a flipchart-sized sheet of paper. (see more)

Q

Quick Design Session

When "simple design" choices have far-reaching consequences, two or more developers meet for a quick design session at a whiteboard. (see more)

R

Refactoring 

Refactoring consists of improving the internal structure of an existing program's source code, while preserving its external behavior. (see more)

Relative Estimation

Relative estimation consists of estimating tasks or user stories by comparison or by grouping of items of equivalent difficulty. (see more)

Role-feature-reason

The "role-feature-reason" template is one of the most commonly recommended aids to write user stories: As a ... I want ... So that ... (see more)

Rule of Simplicity

Rules of Simplicity is a set of criteria, in priority order, proposed by Kent Beck to judge whether some source code is "simple enough." (see more)

S

Scrum

Scrum is a process framework used to manage product development and other knowledge work. (see more)

Scrum Master

The scrum master is responsible for ensuring the team lives agile values and principles and follows the practices that the team agreed they would use. (see more)

Scrum of Scrums

A technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into Agile teams of 5-10. (see more)

Sign Up for Tasks

Members of an Agile development team normally choose which tasks to work on, rather than being assigned work by a manager. (see more)

Simple Design

A team adopting the "simple design" practice bases its software design strategy on a set of "simple design" principles. (see more)

Story Mapping

Story mapping consists of ordering user stories along two independent dimensions. (see more)

Story Splitting

Splitting consists of breaking up one user story into smaller ones, while preserving the property that each user story separately has measurable business value. (see more)

Sustainable Pace

The team aims for a work pace that they would be able to sustain indefinitely. (see more)

T

Task Board

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)

Test Driven Development (TDD)

"Test-driven development" is a style of programming in which three activities are tightly interwoven: coding, testing (in the form of writing unit tests) and design (in the form of refactoring). (see more) 

Team

A "team" in the Agile sense is a small group of people, assigned to the same project or effort, nearly all of them on a full-time basis. (see more)

Team Room

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)

Three C's 

"Card, Conversation, Confirmation" is a formula that captures the components of a User Story. (see more)

Three Amigos

Three amigos refers to the primary perspectives to examine an increment of work before, during, and after development.  Those perspectives are Business, Development, and Testing. (see more)

Three Questions

The daily meeting is structured around some variant of the following three questions: What have you completed? What will you do next? What is getting in your way? (see more)

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)

U

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)

Unit Testing

A unit test is a short program fragment written and maintained by the developers on the product team, which exercises some narrow part of the product's source code and checks the results. (see more)

Usability Testing

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)

User Stories

In consultation with the customer or product owner, the team divides up the work to be done into functional increments called "user stories." (see more)

V

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)

Version Control

Version control is not strictly an Agile "practice" insofar as it is now widespread in the industry as a whole. But it is mentioned here for several reasons. (see more)