MOD Crest
AOF Acquisition Operating Framework

The high level principles and information that guide how the UK MOD Defence Acquisition Community works

version 3.1.1 – September 2010

Content

Key Policies, Processes and Tools for Project and Programme Management (PPM)

Through Life Management

Through Life Management (TLM) focuses on the management of the capability and its component projects, products or services across the acquisition lifecycle (for example CADMID / CADMIT).

TLM covers projects and business-as-usual activities and is the core planning tool, integrating all Defence Lines of Development. The Through Life Management Plan (TLMP) is the key to Through Life Capability Management which may require the integration of a number of project TLMPs.

Integrated Project Management

The complexity of MOD projects and programmes requires Teams to be formed by drawing together expertise from the principal functions managed under the leadership of a Team Leader, Programme Manager or Project Manager.

The TLMP is the primary tool used to delivery integrated project and programme management. It contains the baselines, plans, strategies, data and information necessary to demonstrate control and from which all status reports and forecasts are made.

It is the role of the Project Management Team to ensure that the

  • TLMP is appropriate to the size of the project.
  • TLMP contains the relevant strategies, plans and baselines.
  • Data and Information generated is accurate.

When Industry become a part of the project it is important that they play their role by contributing to the management arrangements and core functions.

A Project Support Office or Project Management Office controls and brings together all the components of the TLMP including:

  • The Requirement:
    • URD / SRD
    • Mandates, Briefs, Blueprints
    • Assumptions.
  • Plans:
    • Programme / Project
    • Acceptance / Benefits Realisation
    • Communications.
  • Outputs from Management Tools:
    • Risk Register
    • Issue Register
    • EVM analysis.
  • Management strategies and arrangements for:
    • Change
    • Stakeholder engagement
    • Issues resolution
    • Risk Management
    • Benefits
    • Acceptance
    • Technology
    • Resource
    • Planning and Control
    • Quality
    • Information Management
    • Acquisition / Procurement.

The TLMP must contain an Executive Summary which comprises of:

  • Project Overview
  • Assumptions
  • Management Strategies
  • Through Life Support Solution
  • Key Risks and Issues
  • Costs and Output
  • Stakeholder Matrix

The requirement for an Executive Summary is mandated for all Category A to C projects within Defence Equipment and Support (DE&S).

The TLMP contents list is not exhaustive, other strategies and plans may be considered for inclusion, for example Modelling and Simulation.

Assumptions Management

Assumptions Management is the generation and maintenance of the Master Data Assumptions List (MDAL). This is a key reference document for both project and programme costing and control.

It is important that the management process involves all key stakeholders.

Resource Management

Within MOD the two key resource factors – budget and manpowerExternal link to Ministry of Defence Intranet content – are controlled by specialist staff using corporate processes. These staff must be fully involved with the:

  • Project planning
  • Change control processes
  • Reporting mechanisms.

Change Control

Change Control is key to maintaining coherence and integrity within the project.

The key features of Change Control are:

  • The formal proposal of change.
  • Appropriate visibility of proposal.
  • Project wide assessment of impact.
  • Formal sanction of the proposal by key stakeholders.

Configuration management of project documents and data sets is important to the control of change and the establishment of baselines.

It is important that the impact of project and programme change is monitored through a corporate performance mechanism.

Information and Knowledge Management

MOD projects are dependent on the generation and control of information.

Information Management processes (including document configuration control) ensure that information:

  • Is stored appropriately for retrieval.
  • Has a clear statement of currency.
  • Is reviewed periodically.

It makes sure that legislation such as Data Protection and Freedom of Information (FOI) Acts are complied with. The availability of good information is the basis for Knowledge ManagementExternal link to Ministry of Defence Intranet content processes.

Information and Knowledge Management applies to:

‘any person, project or system that will be storing or exchanging information within the MOD communication and Information System (CIS) or between the MOD and external applications.’

Joint Service Publication (JSP) 329External link to Ministry of Defence Intranet content defines the requirement and sets the standards by which information is exchanged, reducing the need for interfaces. Contact the Information Coherence Authority for Defence (ICAD) helpdesk on +44 (0) 1793 555391 if you have any further queries on this subject.

Stakeholder Management

The Stakeholder Management Process has two key products:

  • Stakeholder Management Strategy
  • Communications Plan

They will include strategies on how to deal and communicate with all stakeholder groups who have anything to do with the project or programme; not just the Key Stakeholders. The strategies should be based on stakeholder mapping.

Project Quality Management

Project Quality Management is the discipline that makes sure the outputs of the project and the processes by which the outputs are delivered meet the required needs of stakeholders.

The Project Team Leader is responsible for Managing Quality and must comply in full with Mandated Requirements for Quality instructions.

Requirements and Acceptance

Requirements and Acceptance processes capture, analyse and test the documented statement of the User’s needs.

Requirements are a statement of the need the project must satisfy and must be:

  • Well structured
  • Comprehensive
  • Traceable
  • Measurable
  • Justifiable
  • Clear
  • Testable.

Acceptance must allow the stakeholders to agree that the project has satisfied the agreed User’s needs in an objective manner.

Interoperability is a mandated Key User Requirement and the use of Open Systems Architectures is a key enabler for this. For projects with Communication and Information Systems (CIS) content JSP 600External link to Ministry of Defence Intranet content must be used.

Planning and Scheduling

The Planning and Scheduling process underpins all activities in the development, management, control and delivery of projects.

Planning and scheduling is an iterative process and will need to be repeated many times throughout the life of the project. Key features of the planning and scheduling process are:

  • A set of plans required for all projects based on the TLMP.
  • Effective communication with Stakeholders from the outset to agree project objectives, strategies and assumptions before attempting to develop the schedule.
  • Ownership of all project activities (tasks) must be identified in order to allocate resources.
  • The schedule (resourced plan) must be approved by all project stakeholders to ensure full commitment.
  • A work breakdown structure is essential to understanding the scope and range of project activities to be planned.
  • Learning from previous projects (especially in estimating) is the single most valuable guide for future planning and scheduling.
  • Projects should include clearly identified Anchor Milestones.

Risk Management

Risk Management is the process to identify and assess risks, and to plan and implement risk responses. This enables the project management organisation to minimise threats and maximise opportunities in a cost-effective way.

Key features of Risk Management are:

  • The project manager should establish a Risk Management approach which includes the Customer and Industry and is appropriate to the stage and nature of the project.
  • A Risk Management Strategy and Risk Management Plan must be produced for all Projects and included in the TLMP.
  • Risk Management is an integral part of project management and informs project decisions and forecasts.
  • Acceptable levels of risk exposure should be agreed with stakeholders at all major decision points.
  • Risk ownership should be assigned to the party best able to manage the risk.

Earned Value Management

Earned Value Management (EVM) is a project control process based on a structured approach to planning, cost collection and performance measurement. The process enables the integration of project scope, time and cost objectives and establishes a baseline plan for performance measurement.

The use of EVM is mandatory for the Demonstration phase of new Category A, B and C projects within DE&S. Project Teams must use an EVM Plan at Main Gate approval.

Relevant Legislation

No legislation has been identified as relevant for Project and Programme Management.

Technology Management

Technology Management is part of day to day project management and can be defined as the integrated planning, optimisation, developing maturity and exploitation of technology.

It includes research, the development of new technologies, and the identification and management of the risks and opportunities associated with using technology as part of the solution.

Contacts

Project and Programme Management

Owner

Post
MOD Head of PPM Centre of Excellence

Point of Contact

Post Email Phone
PPM Centre of Excellence Policy Lead DESPTG-COE-Pol@mod.uk
  • Mil: 9352 34320
  • Civ: +44 (0) 30 679 4320
Change History

Change History

The AOF was updated to Version 3.0.0 on 1st April 2010. Individual document Change History pages will detail any changes other than minor editorial amendments.

1 September 2010
Minor amendments to correspond with changes to Risk Management and the Risk Lexicon.
1 November 2009
Minor amendments made for Plain English review.
1 March 2009
Information and Knowledge Management amended.
1 September 2008
Project Quality Management paragraph amended.
1 August 2008
Introduction to Technology Management added.
1 November 2007
E-mail addresses updated due to partial DII migration.
1 June 2007
Contact names deleted in accordance with DDefSy Hd InfoSy Pol advice with regards to potential Security and Data Protection Act issues.