Product roadmap vs backlog, and the MVP, for the CAPM
A roadmap is a plan that shows how a product or service is likely to develop over time, broken into product iterations toward a long-term vision. It is not a backlog, which manages features and tasks in short timeboxes. A minimum viable product is the first working release that solves a core user need.
What a roadmap does
A roadmap makes clear what the team is trying to achieve and the steps toward it, and also what it is not doing. Anyone providing budget or governance needs it to see when and how the team is likely to deliver value to users.
Each product iteration, which GDS calls a mission, has a clear objective and a way to measure progress. Missions are mapped over consistent periods, such as quarters, and phases like discovery or beta are timeboxed.
How a roadmap is kept
The roadmap is created and iterated collaboratively, usually led by the product manager, with the delivery team and stakeholders, using what has been learned from performance analysis and user research. At GDS it is iterated at least quarterly.
Roadmaps capture intent, not solutions. The further away a mission is, the more uncertain it is, and items can be added or dropped. A roadmap should be open where possible, so other teams can spot overlap, avoid duplicated work and share code and patterns.
Roadmaps are not backlogs. A backlog is used by a team to manage the delivery of features and tasks in smaller, timeboxed periods.
Minimum viable product
The US Digital Services Playbook says to ship a functioning minimum viable product that solves a core user need as soon as possible, no longer than three months from the start of the project, using a beta or test period if needed. It also says to release features and improvements several times each month and keep a prioritised feature backlog and bug backlog.
Where the exam catches people
Believing a roadmap lists the solutions to be built: GOV.UK says roadmaps capture intent, not solutions.
Believing a roadmap and a backlog are the same artifact: a backlog manages features and tasks in short timeboxes.
Believing a roadmap is fixed once approved: things can be added to or dropped from it, and it is iterated at least quarterly at GDS.
Believing a sponsor or service owner usually leads the roadmap: GOV.UK says the product manager usually leads it.
Believing an MVP is a prototype: the playbook describes a functioning product that solves a core user need.