Execution Phase : Conduct Execution Phase Gate Review
The purpose of the execution phase gate is to verify deliverable and community readiness for an implementation, to ensure that risks are identified and have a viable mitigation plan, and to verify that the planned deliverables are aligned with prior commitments and expectations The execution phase can be iterated to accommodate multiple product releases or multiple changes to an environment. It is expected that an Execution Phase Gate Review occurs prior to each production implementation. Once all product releases have been completed, the project is ready to enter the closure phase.
|Subject Matter Experts|
* The ISC representative with whom the client will work and who is responsible for driving the request to a point of approval or denial.
- Other phase gate participants may be included depending on the type of project.
- For service level agreements (SLAs)/installed base projects, the project owner is responsible for approval. The project sponsor is usually not involved. However, the role and responsibility assignments to be used should be agreed upon in advance.
- Specific consultations depend on phase and nature of project, but may include ISC resource managers, finance, implementation teams, working groups, audit, and others.
PHASE GATE PRESENTATION
The primary objective of the Execution Phase Gate Review is to present a summary of product and community readiness plans. Community readiness should include training, communications, desktop readiness and support structures in place for end users. The Execution Phase Gate Review should also include a summary of what will be implemented, acceptance test results, and the proposed implementation/production rollout strategy.
Iteration is acknowledged within PMAP as a creative fact. PMAP phase structure is not as linear as it appears. Early analysis is refined, elaborated, and modified as more information becomes available and as relationships become apparent. A balance is struck, however, between iteration and rework.
PMAP specifically accommodates and scales to the needs of a variety of projects through iterative planning and execution. For simpler and smaller projects, a single iteration of planning may be enough to create definitive plans and estimates for the rest of the project. For more complex and larger projects, multiple iterations of planning may be necessary until a comfort level is reached with plans for execution.
Likewise for projects that put into production a single coherent system, a single iteration of execution should be adequate. For projects that involve multiple concrete releases with numerous integration points, each production update necessitates its own phase gate and its own iteration of execution. For example. there should be a phasegate prior to the implementation/Production roll-out of a specific release within the Execution phase.
PHASE GATE PRESENTATION