READING NOTE · UPDATED 2026
Use the glossary alongside a real engineering question
This recovered announcement links to the original Agile glossary, rather than reproducing its definitions. Read a term with a concrete software change in mind. A shared vocabulary should clarify the work: which feedback arrives, which quality check matters, and what you will observe after a practice changes. The glossary retains its historical wording; the field guides provide current exercises.
A practical next step
- Open the complete Agile glossary.
- Choose one term and explain it using a real change.
- Check its meaning with the team before selecting a practice.
This 2026 reading note is written by the Durnall editorial team. Richard Durnall’s original text follows below.
Original publication: .
Original WordPress feed timestamp, UTC; the old theme’s local date may differ. Check the date source ↗
The original words below retain their period and attribution. The reading note above is the current editorial addition.
Source capture · 2008-03-12 ↗I’ve published my first cut of an Agile Glossary. You can navigate to it from the main menu at the top of the site or you can go directly by clicking this link ‘Agile Glossary‘.
Let me know of anything missing or anything you think I should include. My reading list and an area to share documents, templates and presentations will follow shortly.