The Most Common Agile Glossary (Clear Definitions for Modern Teams)
Agile teams rely on collaboration and regular communication. But a conversation can quickly become confusing when people use the same word to mean different things.
Does “done” mean the coding is finished, the work has been tested or the feature is available to customers? Is the “backlog” the list of upcoming product work or the work selected for the current Sprint?
Whether you are joining your first Agile team, onboarding colleagues or working across departments, a shared glossary gives everyone a clearer starting point. This guide explains key terms in practical language and shows how to make a glossary useful in everyday work.
Why an Agile Glossary Matters
In busy teams, terminology gets used quickly, but not always consistently. People may nod along while interpreting a requirement, meeting or decision differently.
A shared glossary can help:
- Reduce confusion between teams.
- Make onboarding easier for new colleagues.
- Improve communication between engineering, product, design, quality assurance (QA) and leadership.
- Create an accessible reference point across the organisation.
- Support decisions based on a shared understanding.
A glossary cannot remove every misunderstanding. Its value comes from using it to ask better questions and agree what people mean.
Key Agile Terms Explained
Some terms below belong specifically to Scrum, while others are used more widely. Knowing the difference helps teams avoid treating every familiar practice as an Agile requirement.
Agile and Scrum
Key distinction: Agile and Scrum are related, but they are not interchangeable.
Agile: A set of values and principles for software development that emphasise collaboration, working software, responding to change and regular learning.
Scrum: A framework for tackling complex work through short cycles, shared goals and regular inspection and adaptation.
Following Scrum does not automatically make collaboration effective. Teams still need to listen, use feedback and adjust how they work.
Backlogs and Sprints
Key distinction: Upcoming product work and the current Sprint plan serve different purposes.
Product Backlog: An ordered, evolving list of work needed to improve the product.
Sprint: A fixed period of work in Scrum, lasting no more than one month.
Sprint Goal: The single objective that gives the Sprint its focus.
Sprint Backlog: The Sprint Goal, selected Product Backlog items and the Developers’ plan for delivering them.
User Stories, Acceptance Criteria and Done
Key distinction: Describing a user’s need, agreeing expected behaviour and meeting quality standards are connected tasks.
User story: A short description of a need from the user’s perspective, used as a starting point for discussion.
Acceptance criteria: Specific, testable conditions an item should satisfy to meet the agreed expectations.
Definition of Done: The quality standards an Increment must meet to count as completed work in Scrum. An Increment is a usable addition to the product.
Refinement and Retrospectives
Key distinction: Clarifying upcoming work and improving how the team works have different aims.
Backlog refinement: Ongoing work to clarify, break down and add useful detail to Product Backlog items.
Sprint Retrospective: A Scrum event where the team inspects how it worked and plans improvements to quality and effectiveness.
A refinement conversation might uncover uncertainty about a feature. A retrospective might reveal that unclear terminology repeatedly causes confusion and lead the team to improve its glossary.
Download the Agile Glossary
You can download the Coded Female Agile Glossary and use it as a starting point for your team’s reference.
How to Make a Glossary Useful
A glossary is most useful when people can find it, question it and connect its definitions to real work.
- Start with terms that cause confusion. Include familiar words such as “ready”, “done” and “release”, as well as formal terminology.
- Add a practical example. Show what the term means in your product or team.
- Include it in onboarding. Give new colleagues an accessible reference and invite questions about unfamiliar language.
- Make it easy to find. Link it from the team’s usual workspace or onboarding documents.
- Review it when misunderstandings surface. Use retrospectives to identify definitions or examples that need attention.
For established framework terms, keep the recognised definition and add your local example separately. If your team uses a word differently, explain that difference rather than presenting it as the standard meaning.
Closing Thoughts
A shared vocabulary is a practical way to strengthen collaboration. When people understand what a term means, they can discuss expectations and decisions with less guesswork.
Use this glossary as a foundation and let it grow with your organisation. Review it during retrospectives, incorporate it into onboarding and keep your examples relevant as your ways of working evolve.
Try this with your team: choose three terms you use regularly and ask everyone to write a short definition independently.
Compare the answers. Where they differ, agree the meaning, record an example and add it to your shared reference. Start with “done” if you want a useful conversation.
Definitions are introductory summaries. For the underlying values and framework terminology, see the Agile Manifesto and Scrum Guide.
Further references: Agile Alliance’s user story explanation and the Scrum Alliance glossary. The wishlist examples are illustrative.
You May Also Like
Unleashing the Power of OKRs: Setting Objectives and Key Results for Tech Success
Building a Product-Centric Organisation: A Real-World Guide, Inspired by Apple
