15 Key Terms in Agile Methodologies Everyone Should Know
Agile Methodology
Agile is often misunderstood as a set of meetings or as a faster version of traditional project management. At its core, Agile is a way of organizing work around short feedback cycles, customer value, learning, and adaptation. Frameworks such as Scrum and Kanban provide different structures, but many of the underlying ideas are shared.
The 15 terms below move from Agile’s basic unit of value through planning, flow, feedback, quality, and improvement. They are useful for software teams, product teams, and anyone working in an environment where requirements and priorities can change as people learn.
1. Product Backlog
A product backlog is an ordered list of work that may be needed to improve a product. It can contain features, defects, technical work, research, and other items.
The backlog is not a fixed long-term contract. It changes as the team learns from users, technology, business priorities, and completed work.
2. User Story
A user story is a concise way to describe a need from the perspective of a user or stakeholder. It is often written in a simple format such as: As a user, I want a capability so that I receive a benefit.
The value of a user story is not the sentence itself. The story creates a starting point for conversation about intent, acceptance, and value.
3. Acceptance Criteria
Acceptance criteria describe the conditions that must be satisfied for a backlog item to be accepted. They make expectations testable and reduce ambiguity.
For a password-reset story, criteria might cover identity verification, link expiration, successful reset, and error handling.
4. Sprint
In Scrum, a Sprint is a fixed-length event in which the team works toward a Sprint Goal and creates a usable increment. Sprints are typically one month or less.
The timebox creates a regular feedback rhythm. Instead of planning a large body of work once and waiting months for validation, teams inspect results frequently.
5. Sprint Goal
The Sprint Goal describes the objective the team intends to achieve during a Sprint. It gives the selected work a shared purpose rather than treating the Sprint as a random list of tickets.
If individual items must change during the Sprint, the goal helps the team decide what adjustments still preserve the intended outcome.
6. Increment
An Increment is a concrete step toward the product goal. In Scrum, each increment should be usable and meet the team’s Definition of Done.
A Sprint can produce more than one increment. The key idea is that work should add real, integrated value rather than remain partially complete across many stages.
7. Definition of Done
The Definition of Done is a shared description of the quality conditions that an increment must meet before it is considered complete.
Get Bishal Goutam’s stories in your inbox
Join Medium for free to get updates from this writer.
It may include coding, testing, security checks, documentation, integration, and deployment readiness. A common Definition of Done prevents teams from using the word ‘done’ to mean different things.
8. Backlog Refinement
Backlog refinement is the ongoing activity of clarifying, splitting, estimating, and reordering backlog items so future work is better understood.
Refinement is not about fully specifying months of work in advance. It keeps enough near-term work ready while allowing future items to remain flexible.
9. Daily Scrum
The Daily Scrum is a short Scrum event for Developers to inspect progress toward the Sprint Goal and adapt their plan for the next day of work.
It is not intended to be a status meeting for a manager. Its purpose is coordination and planning by the people doing the work.
10. Sprint Review
The Sprint Review is an opportunity to inspect the outcome of the Sprint with stakeholders and discuss what to do next.
The team can demonstrate completed work, examine changes in the environment, gather feedback, and adjust the product backlog.
11. Sprint Retrospective
The Sprint Retrospective focuses on improving how the team works. The team inspects people, interactions, processes, tools, and quality practices and chooses improvements for future Sprints.
A useful retrospective produces specific changes rather than a list of complaints that never affects the next cycle.
12. Velocity
Velocity is a planning measure some Agile teams use to describe how much estimated work was completed in a Sprint, often in story points.
Velocity can help a stable team forecast its own near-term capacity, but it is not a universal productivity score and should not be used to compare teams.
13. Kanban
Kanban is a method for managing flow by visualizing work, limiting work in progress, and improving how items move through a system.
A Kanban board might show Requested, In Progress, Review, and Done. The important part is not the board itself but the visibility of flow and the constraints placed on unfinished work.
14. Work in Progress (WIP) Limit
A WIP limit restricts how many items can be active in a workflow stage at one time. It encourages teams to finish work before starting more.
If a testing column has a limit of three and already contains three items, the team should help move those items forward rather than pushing additional work into the queue.
15. Cycle Time
Cycle time measures how long a work item takes to move from the start of active work to completion. It is a core flow metric in Kanban-style systems.
Shorter and more predictable cycle times can improve responsiveness. Teams often examine blocked work, handoffs, queue size, and WIP when trying to reduce cycle time.
