You have to present your IT project roadmap to the executive committee, and all you have is a detailed schedule several hundred lines long. The committee does not need the tasks. It wants to know what will be achieved, by when, under what conditions and with what assurance.
That is the purpose of an IT project roadmap: a one-page view that links the project’s objectives to dated milestones, shows what each milestone depends on and says how far each date can be relied upon. It is built in a precise order: the objectives, then the milestones, the dependencies, the capacity, and finally the level of certainty of each deadline. It is then updated at a fixed pace, otherwise it stops describing the project.
Where the IT project roadmap ends and the schedule begins
The roadmap and the schedule are not aimed at the same readers. The schedule organises the team’s work: tasks, sequences, assignments. The roadmap speaks to the sponsor, the steering committee, the business and neighbouring projects. It covers the whole duration of the project, shows only results and milestones, and its precision decreases with distance.
The two documents remain linked by a rule: each roadmap milestone appears in the schedule, at the same date. When they diverge, the committee decides on a picture that the team no longer follows.
The word covers other objects. An IT systems roadmap is the view that brings together the projects of an entire department: it belongs to the portfolio, whose vocabulary is set out in our entry on PPM. A product roadmap follows a product with no end date. Here we are dealing with a single project, bounded in time.
Objectives first, milestones next
Construction begins with what the sponsor expects from the project, expressed as an observable state. “Deploy the invoicing module” describes an activity. “Branches issue their invoices from the new tool” describes a result, which someone will be able to observe. A roadmap carries a short list of such objectives, taken from the mandate or the business case. If the sponsor cannot state them, construction stops there: no drawing will replace that answer.
Next come the milestones. A milestone is a verifiable state at a date: “acceptance signed off with no blocking reservation”, whereas “acceptance” refers to a period of work. Each is attached to an objective, carries an observation criterion and the name of the person who will observe it. Only the milestones where someone decides, receives or commits appear on the roadmap: go-live, cutover, contractual or regulatory deadline.
The order of the milestones deserves examination. A sequence that puts a first part into service early, then extends it, gives the project opportunities to correct that a single delivery at the end of the journey does not offer. On a programme, these stages structure the overall trajectory, described on our page on programme management.
Dependencies and capacity put the draft to the test
A first draft is only an intention. Two checks confront it with what does not depend on the project.
The first concerns dependencies. For each milestone, the project manager notes what must be true beforehand: another project’s delivery, a technical environment, a supplier, a regulatory date, a period when the business is unavailable, such as a financial close. Only dependencies that cross a boundary (team, project, organisation) appear on the roadmap; the internal sequence of tasks stays in the schedule. Each has a counterpart on the other side, who has confirmed their date or has not yet done so. The document shows this difference.
The second concerns capacity. The people the project needs during the planned periods (architect, security expert, key users for acceptance testing) also work for operations and for other projects. The project manager cannot decide alone: their roadmap is a request addressed to those who allocate these skills. When the organisation arbitrates its projects together, the confrontation takes place at that level, according to the mechanisms presented on our page on project portfolio management. Failing that, they obtain a written reservation from each team manager, period by period.
These two checks move milestones, reduce a scope or reveal a trade-off to be requested. They come before any announcement of a date.
A level of certainty for each deadline
Not all the dates on a roadmap have the same value, and the reader must be able to tell them apart. A three-level convention is enough:
- committed: the scope is fixed, the dependencies are confirmed, the capacity is reserved;
- forecast: the estimate exists, some conditions remain to be met, and the deadline is expressed as a period (a month, a quarter);
- envisaged: the order and intention are set, without a date.
Other conventions exist: only two levels (firm, indicative), or a date range per milestone. What matters is that the legend appears on the document and that each deadline falls under it.
The PRINCE2 method offers support: the steering committee authorises only one stage of the project at a time. The firm commitment can cover the authorised stage, and the forecast what follows it. The project manager proposes the level of each deadline; moving to “committed” is for the sponsor and the committee, since that date will be repeated outside the project.
What each step produces, and who is accountable for it
| Step | What it produces | Who is accountable |
|---|---|---|
| Objectives | A short list of expected results, each with its observation criterion | The sponsor |
| Milestones | Verifiable, dated states, each attached to an objective | The project manager |
| Dependencies | The links that cross a boundary, with their date of need and their status, confirmed or not | The project manager for the record, the counterpart of each dependency for its date |
| Capacity | The periods when shared skills are reserved, and the gaps to be arbitrated | Team managers, or the portfolio body |
| Levels of certainty | A legend, applied to each deadline | The project manager proposes, the sponsor and the committee approve the commitments |
| Update | A dated version and the list of changes since the previous one | The project manager, or the project PMO |
Keeping the roadmap up to date
The roadmap is reviewed before each committee, at the pace of the steering cycle. It is also reviewed without waiting when a fact contradicts it: a dependency slips, a trade-off changes the scope, a reserved skill is withdrawn.
Each version carries a date and the list of what has changed: milestones reached, with their observation; milestones moved, with the cause; deadlines that have moved from one level of certainty to another. Previous versions are kept, because the path of a date from one version to the next informs the committee as much as its current value.
One rule distinguishes updating from rewriting. The project manager adjusts a forecast deadline and flags it. Moving a committed deadline is a committee decision, prepared as such: options, consequences, deadline for deciding. Our article on the project review describes the session at which this request is presented.
On a roadmap that already exists, the next update can begin with the legend: classify each deadline shown (committed, forecast or envisaged), then submit this classification to the sponsor. The dates they cannot consider committed point to the dependency confirmations and capacity reservations to be obtained first.