Resources · glossary
Backlog
An ordered list of everything still to be built, from most to least important. It is not a collection of ideas; it is an order.
- backlog
- product backlog
- task backlog
- priority list
- 01
Ordered, not collected
A list without an order is a notebook. A backlog gets its value from someone having decided what comes first, and from the rule that every new idea must name what moves down because of it.
- 02
Who decides
The client, not the vendor. The order follows from what brings in money or removes risk, and nobody from outside can decide that for you.
- 03
Detail grows towards the top
Tasks for the next cycle are described in detail, later ones in a single sentence. Adding detail to an item that will wait six months is wasted work: half of them will never be built.
- 04
A warning sign
A backlog that only grows. Items that sit for a year without moving are not a plan but clutter. Close them rather than carrying them forward forever.
In practice
- ServiceSoftware developmentCustom software for companies of 30–300 people: internal systems, integrations and process automation — and when building beats buying.
- ArticleTaking over a software project from the previous vendor — what to hand over, what to check in two weeks, fix or rewriteA software handover checklist for taking over a project: what the previous vendor hands over, a two-week review, then fix or rewrite.
Related terms
- Product ownerThe person on the client's side who decides the order of work and signs off the results. One person with the authority to decide, not a committee.
- 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.