Definition of the IT master plan
The IT master plan, or information system master plan (in French, SDSI), is a planning document. It sets, for several years, the broad lines along which an organisation’s information system will evolve, the projects to be launched and the resources allocated to them, consistently with that organisation’s strategy.
The expression also refers to the work that produces this document. The methodological guide to information system governance that Amue (the French agency for the pooling of resources among universities and institutions) published in 2008 speaks of an approach that sets, over the medium term, the broad lines of that evolution. It accepts two forms, from a reasoned roadmap to a more elaborate master plan. The names “IT strategic plan” and “digital master plan” are also encountered.
What a master plan is for: choosing before committing
The document is used to decide, for a given period, what the information system should become and what the organisation devotes to it. It gives senior management, the business and the IT department the same list of priorities, and makes visible the requests that have been set aside or postponed. The Amue guide attributes to it in particular the management of priorities in the institution’s interest and the reduction of the risk of unnecessary investment.
It also gives the project portfolio its initial composition. The decisions that follow, project by project, are a matter for project portfolio management.
The document’s sections and its horizons
By way of example, the standard outline in the Amue guide has seven sections: general context, strategic framing, current-state assessment, statement of needs, orientations, multi-year budget, governance bodies. The current-state assessment includes the information system map; the orientations name the projects to be launched and the resources to allocate to them.
The same guide breaks the notion down into three horizons.
| Level | Horizon according to the guide | What it sets |
|---|---|---|
| Strategic master plan | Three years or more | Stakes, priorities, major workstreams |
| Operational master plan | Three years | Projects, budgets, human and financial resources |
| Annual IT plan | The coming year | The year’s work, the reference for the IT budget |
These sections and durations come from a sector guide; each organisation sets its own. The guide adds two requirements: update the master plan regularly, since its framing changes, and manage its delivery.
IT master plan, architecture approaches, API management, roadmap: not to be confused
Enterprise architecture and IT urbanisation are ongoing activities. They produce the map and the target; the master plan uses them, then decides what will be funded, in what order and over what period.
API management is a technical discipline and a family of tools. Implementing it may be one of the workstreams of a master plan, like a migration or a master data repository.
A project roadmap covers only that project: our article on the IT project roadmap describes how it is built. The master plan differs from the project portfolio, whose vocabulary is set out in our entry on PPM: the plan fixes a list at a given date, the portfolio reviews it at regular intervals.
Take a manufacturer whose management software package is reaching end of support
Take a manufacturing company whose management software vendor has announced the end of support. Senior management asks what needs to be launched, and in what order. Besides this deadline, the current-state assessment finds maintenance applications that differ from one plant to another. The gathering of needs brings up a request from customers: batch traceability.
Two scenarios are examined: replace the software package first, or harmonise maintenance first. Senior management chooses the first, which the deadline imposes. The master plan records this choice, the order of the projects, each year’s budget and what is postponed. Every subsequent request is read against this list.
The map, the target and the trajectory on which a master plan draws are described on our IT architecture page.