Engineering roadmap template — editable, free
An engineering roadmap sits between the product roadmap and the tracker: real dates, visible dependencies, and items sized in weeks instead of sprints. This one groups eleven items by system across four lanes, draws the dependency chain, and carries one announced switch-off date as a milestone.
| View | Groups by | Visible fields |
|---|---|---|
By system (timeline) | System | Name, Owner, Status, Start, End |
Leadership (timeline) | System | Name, System, Start, End |
By status (board) | Status | Name, System, Owner, End |
All items (table) | Nothing — one flat list | Name, System, Status, Owner, Start, End |
What does this show that a product roadmap doesn’t?
Overlap, and the queue behind a blocked item. The data lane here has three items scheduled one after another behind a Postgres upgrade, and the upgrade is drawn at its real length. When it moves, everything behind it moves, and that’s visible on the page instead of discovered three weeks later.
Exact dates make that possible. Quarters average the information away: two items both landing in Q4 isn’t a finding, and it’s the only finding a quarter-resolution chart can give you.
What is in this template?
Eleven items across four systems — API, data, web client and infrastructure — with a dependency chain and one announced switch-off date. The API v1 deprecation is a milestone because it was given to customers, which makes it the one date on the page that can’t move, and the reason the two items in front of it have no slack.
One item is blocked. That’s deliberate: the blocked item is what a timeline at this resolution is for, and a template where everything is fine teaches nothing.
Where does this stop and the tracker start?
At the link field. An item here names something worth a fortnight and points at the ticket where it is decomposed. Roadmap for engineering team works through the one field worth turning off on this view — and it isn’t the one people expect — along with why status belongs at item level only.
The boundary between the two documents is worth being deliberate about, because getting it wrong gives you two systems holding the same status and one of them always stale. Roadmap vs project plan draws it on the revision rule instead of on the fields.
For a shorter window at week resolution, a monthly roadmap template is the tighter fit. For the estate rather than the product — upgrades, replacements and the things you are turning off — an IT roadmap template is organised around lifecycle. And the document this one hangs off is usually a product roadmap template , where the items are problems rather than systems.
Common mistakes
Using quarters. A quarter tells you two items happen between January and March; it doesn’t tell you they overlap for three weeks in February with one person on both, which is the entire question.
Turning the dependency arrows off because the picture is cleaner. It moves the discovery to standup a fortnight later, at a much higher price.
Letting items shrink to ticket size. When something is small enough for a pair to finish in a sprint it belongs in the tracker, and leaving it here gives you two systems holding the same status.
Filling in the owner column in advance. An item with nobody against it’s either unowned or unstaffed, and both need saying out loud instead of papering over.
Questions
Is this a roadmap or a plan?
A roadmap, and the test is the revision rule instead of the resolution. You can move an item here in a meeting. A document that needs a written change and a distribution list is a plan, however coarse its dates are.
Why group by system instead of by squad?
Because systems outlive team structures. A roadmap grouped by squad has to be redrawn the week somebody reorganises, and the dependency chain — which is the reason to draw this at all — runs between systems, not between teams.
What about the announced deprecation date?
It stays exact and gets marked as a milestone. A date already given to customers is a commitment instead of an estimate, and drawing it’s what makes the absence of slack in front of it visible.
Related
- Monthly roadmap templateFour workstreams across one month at week resolution, and the point where this stops being a roadmap.
- Roadmap for engineering teamThe view that hides almost nothing, the one field to turn off, and where the tracker starts.
- Roadmap vs project planDifferent units, different revision rules, and how to tell which one is being asked for.
Last updated