Blueprint design and delivery is one of the Governance Themes that are fundamental to MSP. The Blueprint is a statement of the intended state of affairs after completion of the programme, and is designed during the Defining a Programme stage. Along with the Benefits Realisation Plan and high level corporate goals, it forms the basis of the Business Case.
Our MSP Foundation and MSP Practitioner courses will teach you about Governance Themes, including Blueprint design & delivery. As well as giving you this theory, our trainers will give you real life examples and case studies, so you’ll be able to put your new knowledge into context straight away!
What goes into the Blueprint?
The Blueprint is a model of how the organisation works, including it’s working practices/processes, the information it needs to function, and of supporting technology needed. The Blueprint designed during the Defining a Programme stage clearly demonstrates what the programme will achieve, and is referred back to throughout the life of the programme in order to maintain focus.
The final Blueprint will usually also include outlines of how the state of operations will be at the end of each Tranche.
The P.O.T.I. model is used for Blueprint design in MSP
- Processes – Business models of operations and functions, and how these will fit with or change operational processes.
- Organisation - The structure of the programme and how it fits into the organisation as a whole; including staffing levels, roles and skill requirements, the organisational culture, and supply chain details.
- Technology – IT systems, buildings, equipment, machinery, accommodation.
- Information - Informational/data requirements from the programme and business operations, including measures of performance.
The Purpose of the Blueprint
The Blueprint is referred back to during each stage, particularly at the end of each Tranche, and ensures a focus on benefits and the required organisational structure after the programme. Because this goes beyond simple goals or milestones, it means that everyone working on the programme can share the same high-level vision.
As the Blueprint only covers new capabilities, there should be minimal temptation to think of the old/current state of affairs – so everyone on the Programme is looking forward to a shared vision, not back.
What Happens to the Blueprint After Programme Definition
Once the Blueprint has been finalised and the programme defined, the Programme Plan will deliver the state as outlined in the Blueprint, using Gap Analysis – consideration of the differences between the blueprint and the current situation, to plan the programme.
Each Tranche of the programme will deliver part of the future state as outlined in the Blueprint, and each capability is reviewed between the Tranches with reference to the final Blueprint.
When the programme is closed, the current state of affairs is compared to the Blueprint design – of course, the two should match up. Where there are differences, these are recorded as learning points for future programmes or corporate strategy.