Program Roadmap: Sequence Components by Benefit Date

A program roadmap is the chronological view of a program's components, the dependencies between them, the gates where decisions are taken, and the date each benefit is expected. A project schedule lists tasks until one deliverable is handed over. A program roadmap continues past delivery, to the date the benefit shows up in the business.

Some terms, defined once:

• A program is a group of related projects and work managed together to obtain benefits that managing them separately would not.
• A benefit is a measurable improvement the organisation gains, such as cash released or cost removed.
• A gate is a formal decision point at which the sponsor decides whether to continue, change or stop.

The level of detail also differs. A project schedule works in days and tasks. A program roadmap works in quarters and components.

A paper in the Project Management Institute (PMI) library, presented at the PMI Global Congress 2015, names as a best practice a roadmap that sets out the interdependencies between work under way and the milestones for when each benefit is to be realised (Levin, PMI Global Congress paper, 2015).

Two scope notes. This page covers a single program. Portfolio management decides which programs and projects to fund, and our guide to how program and portfolio management differ covers that decision. How several agile teams share one program outcome is covered in our guide to agile program management.

A benefit-sequenced program roadmap is a table with one row per component. Each row shows what the component needs first, which benefit it enables, who owns the component, when it delivers, when the benefit lands and who owns the benefit. Copy the columns into a spreadsheet and you have the template.

The program below is our illustration, not data from a real program. It is a ₹30 crore order-to-cash modernisation for a dealer network. It starts in the first quarter (Q1) of financial year 2028 (FY28), which is April to June 2027 in the Indian financial year (April to March). It has four benefits:

• B1: billing cycle cut from 11 to 4 days, releasing ₹6 crore of working capital once. This is our assumption: invoices go out 7 days sooner, so cash arrives 7 days sooner. At about ₹313 crore of annual dealer billing, 7 days of billing is about ₹6 crore (313 × 7 ÷ 365).
• B2: ₹3.2 crore a year less claim leakage.
• B3: ₹2.4 crore a year lower warehouse picking cost.
• B4: ₹1.8 crore a year in retired legacy licence fees.

B1 cannot land before the quarter in which C5 (dealer training) delivers, and B2 lands two quarters after the later of C3 and C5.

The recurring benefits total ₹7.4 crore a year (3.2 + 2.4 + 1.8), plus the one-off ₹6 crore. Our assumptions for the lags are:

• B1 shows at the first full month-end close after go-live (one quarter).
• B2 shows after two claim cycles (two quarters).
• B3 shows two quarters after scanning goes live.
• B4 starts the first quarter after switch-off.
• The legacy licence renews each 31 December, with no early exit.

The costs add up: 1.5 + 12 + 4 + 7 + 1.5 + 4 = ₹30 crore.

Quarter by quarter, the same example reads as follows. D means the component delivers. B1 to B4 mean the benefit lands. Q3 FY29 ends on 31 December 2028, the licence renewal date.

Read the table from the right-hand columns first. The component owner delivers the work. The benefit owner is the business leader whose numbers must change, and who confirms that the benefit has landed. They are rarely the same person. The register that records each benefit's owner and measure is covered in our guide to benefits realisation management, and the roadmap only sequences it.

Where the gates sit in the example. Gate 1 comes at the end of Q1 FY28, once C1 has delivered, to decide whether to release C2’s ₹12 crore, the largest spend. Gate 2 comes at the end of Q2 FY29, when C4 delivers: it is the last point before the 31 December 2028 renewal at which the sponsor can still protect the licence saving.

A one-quarter slip to C4 (warehouse scanning) costs the most, ₹2.4 crore in our model, because it pushes the legacy shutdown past the 31 December 2028 renewal. Move each component one quarter later, follow the dependencies, and write down every benefit whose date changes. A component's own benefit is only part of the answer. Successor components and fixed dates carry the rest.

Large programs often carry live delivery issues, so test the sequence. In the NISTA Major Projects Annual Report 2025-26, 109 of the 189 projects in the UK Government Major Projects Portfolio (58%) were rated Amber at the end of March 2026: delivery appeared feasible, but significant issues needed management attention. A further 34 (18%) were rated Red.

These are the government’s most complex projects and each rating is a snapshot, so read the figures as a warning about complexity, not a forecast.

The rule we apply is that a successor cannot deliver in the same quarter as its predecessor, so it must deliver in a later one. The money effect is our model:

• A quarter of a recurring annual benefit is the annual figure divided by four.
• The one-off B1 is costed at its carrying cost: ₹6 crore × 9% a year ÷ 4 = ₹0.135 crore (₹13.5 lakh). The 9% cost of funds is our assumption.

The most expensive row is not the largest component. C2 is the biggest spend at ₹12 crore, yet a quarter’s delay costs ₹0.935 crore. The ₹7 crore C4 costs ₹2.4 crore.

A project timeline shows C4 as a three-distribution-centre job with one benefit. The slip test shows it as the component that protects the licence saving. We would respond in one of two ways. Either pull C4 forward to Q1 FY29, which the model allows because it needs only C1, so that a quarter of float sits between C4 and C6, or ask the vendor for a shorter renewal term.

A roadmap is built in six steps: benefits and owners, components, dependencies and fixed dates, backward sequencing, gates, and a review rule. Each step supplies the input for the next.

In our view, the commonest cause of failure is a project timeline with a program label. We see four faults, each with a test you can run before you issue the roadmap.

• A relabelled Gantt chart. Test: is there a "benefit lands" column with a date? Fail if bars end at delivery and nothing follows.
• Benefits with no owner. Test: does every benefit name one person, below sponsor level, who signs off that it has landed? Fail on "business", "TBD" or the delivery lead.
• A constant lag. Test: are fixed-date events marked, and does every component due within one quarter of one carry a flag? Fail if lag is one number for the whole program.
• No re-baselining. Re-baselining means formally resetting planned dates after an approved change. Test: does the roadmap show a version date and the last change approved? Fail if dates are overwritten without a record. Approval of a change should sit with the governance body named in the program management plan; our program governance framework shows how to set those decision rights.

A fifth fault is hiding non-project work. In the example, C1 and C5 are ₹3 crore, 10% of the ₹30 crore, and a project timeline often leaves them off.

Program Management Essentials is our foundation course in program management, with structured modules that build program management skills step by step. It is priced at US$99 per enrolment as of November 2026, and pricing varies by market. It is not preparation for the Program Management Professional (PgMP®) exam.

It suits professionals who want a grounded base in program practice before applying it to a roadmap like the one above. You can see the course and its current price in our course store.

If you would like to talk through your goals first, we offer a free discovery consultation before enrolment. It does not itself enrol you in a paid program. Write to support@augmentconsultancy.com or call or WhatsApp +91 9816 360 116.