In Programme Procurement Strategy – 1 I briefly reviewed the approach from the OGC Risk Allocation Model for Project Strategy and Procurement.
Thinking about how to apply that approach to my own programme, I quickly realised that the range of changes we are seeking to deliver (across technology services, business processes and management capabilities) does not easily sit into a single risk assessment.
So I’m still attracted to the risk-based approach, but it is going to need substantial de-composition of the programme to apply it meaningfully.
I need to put together an analysis of procurement options for the programme I am shaping, as first steps in devising a procurement strategy.
The main online reference I have found so far is the OGC’s Risk Allocation Model for Project Strategy and Procurement (pdf).
The first part of that document examines the suitability of different contract types in relation to the nature of the organisation and the programme goal:
On my other blog I’ve been posting my process as I worked through the creation of a Quality Management Strategy.
Post 1 Post 2 Post 3 Post 4 Post 5
One key learning point was that the management of benefits, whilst considered by MSP as a separate activity, is absolutely fundamental to ensuring the programme delivers value, so it is important to make that an integrated part of the Quality management Strategy.
Further reference to the [[MSP]] manual (p77, 2003 version) identifies three areas of programme activities where quality management is involved:
Quality management of the governance arrangements – this corresponds to the top level “Governance Reviews” in post 3 of this series. Quality assurance and review of project outputs – this corresponds to the lower three levels in post 3 of this series. Configuration Management of key programme documentation. Drawing on this we need to add an area to our Quality Management Strategy (item 3 above).
At some point we will have to identify the who of Quality Management – who will carry out all of the activities.
Looking at the last post it occurred to me that a useful simplifying assumption would be to divide the processes into three levels:
Meta-Programme Activities Quality activities which sit outside the programme Programme Activities Quality activities at the programme level Project Quality Activities Quality activities within individual projects
In the last two posts of this series I have started down the line of understanding the value chain of a programme, and therefore what it is we need to quality assure.
This post steps back for a moment to think about the sort of process we need to design in our Quality Management Strategy – the how of quality assurance.
One of the major differences between a programme and a project is the very much higher likelihood of change in a programme than in a project:
Why do we need a Quality Management Strategy?
In an earlier post I wrote about my confusion when starting to think about how to create a quality management strategy for my programme.
Let’s go back to basics – why do we need a Quality Management Strategy?
Fundamentally it’s about ensuring (to an acceptable level of certainty) that the Programme will deliver what it sets out to deliver.
And that is about Value.
I’ve been thinking about how to put together a Quality Management Strategy for the programme I am shaping. Question is, where to start…
The MSP Manual says:
[…] used to define and establish the activities for managing quality across the programme
which sounds tautologous to me. In Chapter 9 on Quality Management, a bit more detail appears: The Quality Management Strategy defines what criteria will be used to assess quality, what quality activities will be incorporated into the management and delivery of the programme, who will be responsible for carrying out these activities, and how the programme will meet required audit and organisational standards for quality assurance and quality control.