Resources · glossary
Agile
An approach in which a project is built in short cycles, each ending with something that works, instead of one release after six months. It assumes the requirements will change along the way.
- agile
- agile development
- agile methodology
- Scrum
- 01
What it changes for the client
You see a working piece every two weeks and can change the order of work. The price of this is real: you cannot get a final figure for a final scope at the start, because the scope is meant to move.
- 02
When it makes no sense
When the scope is known, closed and will not change: a simple brochure site, a content migration. The planning ceremonies then cost more than they give.
- 03
The most common misunderstanding
That agile means no plan or no documentation. It means a different plan: priorities instead of a schedule down to the last day. A project without priorities is not agile, just undefined.
- 04
How to pay for it
Usually on a time & material basis or in fixed sprints at an agreed price. We compare both models with fixed price separately.
Related terms
- ScrumA specific form of agile work: fixed cycles of a few weeks, three roles and four recurring meetings. It is the most popular one, so it is often confused with agile as a whole.
- SprintA closed stretch of work, usually two weeks long, at the end of which something working exists. Its length is fixed: the scope changes, not the deadline.
15 minutes. No sales pitch.
A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.