Project Control Process - Gate review Objectives
•  Three Gate objectives are proposed in order to track
project progress:
–  1. To formally approve the completion of a stage:
To provide assurance that all planned activities for a
stage were completed and met the project plan within
stated limits.
–  2. To ensure closure of any variance that required the
involvement of management, ( that could not be
resolved by the project team ).
–  3. To make or to formally document a decision about
the next stage.
Project Control Process - Gating Overview
Gate N-1
Review
problem
resolutions
Gate N
Review
Completion of
technical activities
Completion of
technical products (GPCR)
Collection of project data
Presentation - Approval
of next Phase
Project Control Process - Gates by IS Life-Cycle
SALC
Account
Management
Initial Investigation
Supplier Evaluation
and Selection
Gate 1
RSD
Account
Management
Installation, Adaptation, Interfacing,
Integration, Acceptance & handover
Launch &
Operation
Detailed Design, Developpment
and Testing
Launch &
Operation
Gate 2
Initial Investigation and
High Level Design
Gate 2a
Gate 0
Gate 1&2
Gate 3
: Gates that require a formal gate review by Gate Review Committee
: Gates that require an ISPO authorisation
Gate 4
Project Control Process - Gate approved means
•  work completed as planned, with no significant
variances,
•  all mandatory products have been completed, and
•  recommendation for next phase is approved.
Else
Project must stay at the current stage,
bridge the gaps and gate again
Project Control Process - IS Variance Policy
“Variance Situation” - when the project actual or the
projected data, exceeds an approved
variance limit.
Progress Variance: Is apparent when technical and management products identified
on GPCR are: Absent, Of very low quality, Not Reviewed/Signed-off or Late.
Quality Variance: Is Apparent when major non-conformance are detected, when IS
life-cycle is not followed, Significant I/R are reported by the independent UAT.
Effort Variance: Is apparent when either too many/too little effort is reported (TRS).
Scope Variance: Is apparent when scope is decreased by the project team to meet a
date. Opposite can also appear “ creeping requirements”.
Cost Variance: Is apparent when % spent (expense or capital) is approaching limit
and no immediate action is foreseen to submit an amendment to CRB
Project Control Process - Gate Review Presentation
“Standard Presentation” - Gate review presentations must
all follow the standard.
Slide 1 - Project Name, Number, Title, Current Stage, Gate #
review, project manager name, Customer name
Slide 2 - HR (IS, Users, External) current, next stage, deviations
Slide 3 - Schedule, current, next stage, deviations
Slide 4 - Costs (Capital, Expenses), current, next stage, deviations
Slide 5 - Architecture & technology diagram
Slide 6 - GPCR completed/outstanding items, current, next stage
Slide 7 - project Risks and recommendation to proceed