Agile Glossary

Ref: Agile Glossary from Agile Aliance

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.
Source: Agile Glossary

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.
Source: Agile Glossary

Antipatterns are common solutions to common problems where the solution is ineffective and may result in undesired consequences.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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. 
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

Customer development is a four-step framework that provides a way to use a scientific approach to validate assumptions about your product and business.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

Exploratory testing is, more than strictly speaking a “practice,” a style or approach to testing software which is often contrasted to “scripted testing.”
Source: Agile Glossary

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.
Source: Agile Glossary

A facilitator is a person who chooses or is given the explicit role of conducting a meeting.
Source: Agile Glossary

An Agile team frequently releases its product into the hands of end users, listening to feedback, whether critical or appreciative.
Source: Agile Glossary

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.
Source: Agile Glossary

The team meets regularly to reflect on the most significant events that occurred since the previous such meeting, and identify opportunities  for improvement.
Source: Agile Glossary

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.
Source: Agile Glossary

 

“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.
Source: Agile Glossary

“Integration” (or “integrating”) refers to any efforts still required for a project team to deliver a product suitable for release as a functional whole.
Source: Agile Glossary

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.
Source: Agile Glossary

An iteration is a timebox during which development takes place. The  duration may vary from project to project and is usually fixed.
Source: Agile Glossary

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).
Source: Agile Glossary

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.
Source: Agile Glossary

A Kanban Board is a visual workflow tool consisting of multiple columns. Each column represents a different stage in the workflow process.
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

A Minimum Marketable Feature is a small, self-contained feature that can be developed quickly and that delivers significant value to the user.
Source: Agile Glossary

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.”
Source: Agile Glossary

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.
Source: Agile Glossary

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

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.
Source: Agile Glossary

Pair programming consists of two programmers sharing a single workstation (one screen, keyboard and mouse among the pair).
Source: Agile Glossary

Personas are synthetic biographies of fictitious users of the future product.
Source: Agile Glossary

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.
Source: Agile Glossary

Agile teams generally prefer to express estimates in units other than the time-honored “man-hours.” Possibly the most widespread unit is “story points.”
Source: Agile Glossary

The product owner is a role created by the Scrum Framework responsible for making sure the team delivers the desired outcome.
Source: Agile Glossary

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.
Source: Agile Glossary

When “simple design” choices have far-reaching consequences, two or more developers meet for a quick design session at a whiteboard.
Source: Agile Glossary

Refactoring consists of improving the internal structure of an existing program’s source code, while preserving its external behavior.
Source: Agile Glossary

Relative estimation consists of estimating tasks or user stories by comparison or by grouping of items of equivalent difficulty.
Source: Agile Glossary

The “role-feature-reason” template is one of the most commonly recommended aids to write user stories: As a … I want … So that …
Source: Agile Glossary

Rules of Simplicity is a set of criteria, in priority order, proposed by Kent Beck to judge whether some source code is “simple enough.”
Source: Agile Glossary

Scrum is a process framework used to manage product development and other knowledge work.
Source: Agile Glossary

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.
Source: Agile Glossary

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

Members of an Agile development team normally choose which tasks to work on, rather than being assigned work by a manager.
Source: Agile Glossary

A team adopting the “simple design” practice bases its software design strategy on a set of “simple design” principles.
Source: Agile Glossary

Story mapping consists of ordering user stories along two independent dimensions.
Source: Agile Glossary

Splitting consists of breaking up one user story into smaller ones, while preserving the property that each user story separately has measurable business value.
Source: Agile Glossary

The team aims for a work pace that they would be able to sustain indefinitely.
Source: Agile Glossary

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.
Source: Agile Glossary

“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).
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary

“Card, Conversation, Confirmation” is a formula that captures the components of a User Story.
Source: Agile Glossary

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.
Source: Agile Glossary

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?
Source: Agile Glossary

A timebox is a previously agreed period of time during which a person or a team works steadily towards completion of some goal.
Source: Agile Glossary

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.”
Source: Agile Glossary

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.
Source: Agile Glossary

Usability testing is an empirical, exploratory technique to answer questions such as “how would an end user respond to our software under realistic conditions?”
Source: Agile Glossary

In consultation with the customer or product owner, the team divides up the work to be done into functional increments called “user stories.”
Source: Agile Glossary

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.
Source: Agile Glossary

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.
Source: Agile Glossary


Ref: Agile Glossary from Agile Aliance