In short
A traditional IT organisation produces a lot of documents: an annual plan, quarterly plans, project plans, roadmaps, change requests. We make planning simpler. There is one shared backlog, and that is the development agenda of the business.
What goes on the backlog
Everything the business wants from IT: small improvements that matter next week, but also ideas whose turn may not come for another two years. Each backlog item describes the desired result, not just the technology.
How the planning emerges
We decide the order by setting priorities together:
- Is the business changing? Then the backlog changes.
- Does a better commercial opportunity come along? Then it moves up.
- Does an idea turn out to have little value after investigation? Then it is not built.
Planning is then not an administrative goal, but a consequence of business priorities.
From backlog to development
Before a backlog item is built, it is clear what it will deliver and what investment it requires. For that we use three types of agreement: a fixed price, a fixed budget with a review point, and a timebox for investigation.
What to watch out for
- Keep the backlog focused on results: "less manual reconciliation" says more than "build an interface".
- Review the priorities regularly together with the management team.
- Dare to drop backlog items. Not building is also a decision.
Would you like advice on your backlog? Request a free advice conversation.
Updated on