About The Agile Dictionary
Welcome to iteration zero of The Agile Dictionary! Our goal with this project is to provide broad, authoritative definitions of common Agile terms. You will note that each definition also includes a section titled “etymology,” where we capture the origins of the term wherever possible.
Visit the definitions by clicking on the letters in the navigation bar, or you can search for a term, above.
e is for...
A large user story that awaits decomposition into smaller stories prior to implementation. Epics are typically stories that are far off on the development horizon, usually lower priority items. When an epic story works its way up the backlog, it is usually decomposed into smaller stories.
NB: One can easily be tempted to associate the term ‘epic’ with importance; in Agile, epic relates only to size.
Mike Cohn coined the term epic as it relates to Agile.
An Agile software development methodology that emphasizes customer involvement, transparency, testing and frequent delivery of working software.
The Extreme Programming canon includes a Customer Bill of Rights and a Developer Bill of Rights, and lists its core values as communication, simplicity, feedback, courage and respect. XP is a developer-centric methodology, and unlike Scrum, it prescribes specific coding practices like Pair Programming, in which two developers work side by side at a single machine, automated unit testing, and frequent integration. Another key practice in XP is refactoring, or the continual improvement of design over many iterations.
The basic advantage of XP is that the whole process is visible and accountable. The developers will make concrete commitments about what they will accomplish, show concrete progress in the form of deployable software, and when a milestone is reached they will describe exactly what they did and how and why that differed from the plan. This allows business-oriented people to make their own business commitments with confidence, to take advantage of opportunities as they arise, and eliminate dead-ends quickly and cheaply. — KentBeck
In 1996, Chrystler’s visionary CIO, Sue Unger, gave Kent Beck free reign to form a team to tackle the Chrystler Comprehensive