The OGC's Managing Successful Programmes (MSP) framework uses a categorization process to identify areas of scope that should be considered by the programme Blueprint.
A Blueprint is a detailed vision for the organisation, covering what the organisation will look like when all the projects are completed, the programme is wound up, and the business transformation is done. Typically, you would only write a Blueprint at a programme level, so project managers will 'inherit' a Blueprint from their programme manager. If you are leading a project as part of a bigger initiative being managed as a programme, ask to see the Blueprint if you haven't already. It will help set your project in the wider context of what the business is trying to achieve.
In particular, Blueprints use the POTI model as a way to define the scope of what is going to change once all the projects in the programme are complete. POTI sets out the scope of the programme at a high level.
POTI stands for Processes, Organisation, Technology and Information. These four areas make up a comprehensive view of all the elements that form the programme scope.
Processes
Projects change processes and introduce new ones. This area of scope covers any operational business models that will change as a result of the work that will be carried out under the programme. This can include:
- Performance levels and output
- The introduction of new ways of working
- The phasing out of old ways of working
- Changes to existing ways of working
Organisation
This area of scope covers the people changes that will result from the projects. This is a broad section and it covers everything to do with personnel from organisational culture to how many employees the company will need when the programme is complete. Examples of items that would be included in this area of scope are:
- New skill requirements for employees
- Culture changes
- Staffing levels
- Employees moving from one role to another
- Training needs
Technology
Technology requirements for the programme fall into this area of scope and will typically be delivered across several projects within the programme. This area, however, covers more than just computers. It also encompasses systems, tools and other resources such as buildings. The sort of things that are included in this scope area are:
Information
This final part of scope covers the mainly intangible area of data. Information required in the new, fully transformed, organisation is noted here. These changes can be hard to establish at the beginning of the programme, so your scope statement may just say 'new information requirements' and these can be defined as stakeholders are engaged throughout the various projects and their reporting and information need become known. As some examples, here is what you could include in this section:
You would expect to see something in each of these four categories as part of the scope statement in the Blueprint. It will be very rare that something will be delivered without having an impact on all of these areas in some form, so if you are writing a scope statement and have some pieces missing, think again about what will be changing as a result of this transformation exercise.
- New computer systems
- Changes to existing technology systems
- Accommodation requirements - procuring or selling off buildings
- Machinery or heavy plant requirements
- Other equipment needs - procuring or selling off equipment
- New networks or toolsets
- New reports
- Changes to existing reports or reporting systems
- Requirements for new data to feed into reports
- Project-specific data outcomes like occupancy rates if you were building a new hotel