Which occurs when the P3O implementation programme is closed?

The closure of the P3O implementation programme signifies that the P3O model has been successfully established and is now fully operational. The temporary programme structure set up to create the P3O is no longer needed because the P3O's functions, services, and processes are now integrated into the organization's standard operating procedures. This transition from a temporary implementation effort to a permanent, self-sustaining business function is known as becoming 'business as usual' (BAU). The programme's closure is the formal milestone marking this successful transition.

A. The Vision Statement is created during the initial stages of the implementation programme to define the end-goal and guide the delivery, not rewritten at the end.
B. The Blueprint is a detailed model of the future P3O, developed during the definition and delivery phases of the implementation, not produced upon its closure.
C. Risks to the implementation are identified, assessed, and managed continuously throughout the entire lifecycle of the implementation programme, not just captured at the end.

AXELOS. (2013). Portfolio

Programme and Project Offices (P3O). The Stationery Office.

Section 9.4.4

Tranche 3 and beyond – embed P3O as Business as Usual (BAU): This section explicitly discusses the final phase of implementation where the P3O becomes a permanent

self-sustaining business function. The closure of the implementation programme is contingent on this state being achieved.

Figure 9.2

The P3O Implementation Lifecycle: This diagram illustrates that the final stage of the lifecycle

following delivery

is the embedding of the P3O as Business as Usual

after which the implementation programme can close.

Section 9.2

The P3O Implementation Programme: This section describes the implementation as a temporary programme designed to deliver a permanent capability. The closure of this temporary structure happens once the capability is delivered and operational.