The Detailed Agile Glossary
Learn the unique terminology used in Agile development from the experts
at Agilemania. Help the Agile community practice continuous learning.
Automated Build or Build Automation is the process of automating the development of the software build and related processes such as collate computer source code consisting binary code, packaging binary code, and carrying out automated tests.
ATDD is a development methodology that promotes good collaboration between the business and technology group. Many similar methodologies work more or less the same way like Behavior Driven Development (BDD), Example Driven Development (EDD) and Specification by Examples, etc. Read More
Business Agility is the ability to excel in the digital age by swiftly responding to market changes and lucrative opportunities with the help of digitally driven business technology.
Backlog Grooming or Product Refinement is a repetitive meeting where product owners, product managers, and the engineering teams sit to prioritize, enhance, and finalize the items before the sprint planning. Read More
Burndown chart is a visual representation of a graph that assesses how much work a development team has done through a user story. Read More
Continuous Integration is the practice of automating the merge of code changes from numerous developers into a single repository.
Class Responsibility Collaboration Cards are a brainstorming tool used to design object oriented software.
Collective Code Ownership
Collective Code Ownership is the principle that every team member is allowed to make changes to the code either to repair a bug, complete a task, or improve the entire code structure.
Customer Development is a 4 step framework to validate the customer needs that a business has identified, build a product that satisfies a customer need, testing the right methids to acquiring and retaining customers, and utilize the right resources to fulfill the demand for the product.
Definition of Ready
Definition of Ready refers to the stage when requirements are met when a story can be moved from backlog to development.
Exploratory Testing is a simultaneous testing where test design and execution is done on the go.
An Epic is a large task that is broken into smaller chunks called user stories that caters to the needs of the end users.
Frequent Releases mean regular releases so that end users can give critical and valuable feedback.
Incremental Development is an approach where a product is broken into small pieces that are functional called Increments
The acronym INVEST stands for Invest, Negotiate, Valuable, Estimable, Small, and Testable. It is a guide to write good user stories.
Iterative Development is the recurring process of development to improve the product.
Iteration in Agile refers to the short time period where a user story is built and tested.
Information Radiator is the disclosure of descriptive information to all the stakeholders and team members which is updated regularly.
A mock object is simulated object that imitates the behaviour of the smallest testable parts of application in controlled ways.
Minimum Marketable Feature (MMF)
Minimum Marketable Feature(MMF) is a small, self sustained feature that must be delivered to the end user to gain value.
A retrospective that takes place at the end of an event or towards the end of a project is known as Milestone Retrospective.
Mob Programming is a collaborative approach where the whole team works together on the same task, at the same time, in the same space, and in the same computer.
Planning Poker or Scrum Poker is an agile technique which helps teams predict the effort needed to complete tasks in the product backlog.
Points (estimates in)
A Point or Story Point is an agile measurment metric to estimate the time required to complete a user story.
A Product Owner is a key individual who is responsible for delivering superior quality products to the end users within the deadline. The product owner is tasked with optimizing the business value of a product by creating and maintaining the product backlog. Read More
A Project Charter is a short formal document that contains project objectives, project scope, and project responsibilities to seek permission from senior management.
Pair Programming is an agile technique where two programmers work together in one work place.
Rules of Simplicity
A set of criteria in the order of priority to determine if the source code is simple and not complicated.
1. The code is validated by automated tests and tests return positive results.
2. The code has no duplication.
3. The code conveys every idea or responsibility individually.
4. The code contains minimum number of components like classes, methods, and lines that comply with the first three criteria.
Relative Estimation is the process of estimating task completion using relative measurement units as opposed to units of time. Read More
Agile Retrospective refers to the meeting that is held at the end of an sprint. Read More
Refactoring refers to the improvement of the internal structure of a current program’s source code.
Scrum is a lightweight framework for building, delivering, and sustaining products in a composite environment. It is a quick, adaptive, and responsive framework that is designed to build products faster and offer value to the customers. Read More
Story Mapping is a technique used in in product ideation, like discovering a new product or new feature in an existing product.
The Scrum Master is responsible for the implementation of the Scrum framework. They ensure that the scrum principles and practices are followed. They eliminate hurdles, conduct meetings, and work with product owners. Read More
Story Spiltting is the division of stories into one user story into smaller user stories.
A Sustainable is a pace that every team functions at and must be respected and adhered to.
Scrum of Scrums
Scrum of Scrums is scaled agile framework.
Sign Up for Tasks
Sign Up for Tasks is an agile term where team members decide what tasks to work on instead being assigned by a reporting manager.
Scrumban is an agile methodology which is the fusion of the best features of Scrum and Kanban.
Sprint Planning is time bound working session which is a duration of 1 hour. It is meeting attended by the Product Owner, Scrum Master, and the Scrum team where the product baclog items that will be worked on during the sprint is discussed. Read More
A Sprint Backlog is a list of tasks finalized by the Scrum team to work on during the current sprint.
The team and the Product Owner has a separate workspace for the duration of the entire project. This exclusive workstation is called the Team Room.
An Agile team refers to the cross functional team which consist of 5-11 members who are responsible for the executing the Agile project.
The daily standup meetings in Agile have the three questions that are constant-What did you work on yesterday? What will you work on today? and Were there any problems that you faced?
Timebox refers to the stipulated time period a task is supposed to be completed.
Three Amigos refers to the meeting of the Product Owner, developer, and Quality tester come toegther to discuss the increment of work before, during, and after the development.
The Three C’s of User Story refers to Card, Conversation, and Confirmation. The Card is written description of the description but not the specific or complete requirements. Conversation refers to the discussion between the Product Owner and the client before the user story is added to sprint backlog for review and approval. Confirmation refers to the acceptance criteria which records the mandatory requirement and converts into test criteria which helps know if the user story is successfully delivered.
A Task Board is visual tool used by individuals, teams, and organization to represent work and its path to completion.
User Story is an aid used in Agile to record the description of software product from the end user perspective.
Unit Tests are the small pieces of code written by thr developers to validate the source code works.
Usability Testing in Agile is to assess the product by getting it tested by the users.
Ubiquitous Language is the practice of developing a rigourous language understood by developers and end users.
Version Control, also called Source Control is the practice of changing and making changes to the code.