More Effective PMO Stage Gates

Home » More Effective PMO Stage Gates

Introduction to Stage Gates

A stage gates process (also known as phase gate) is a common control mechanism associated with IT projects in corporate IT departments.  A series of conceptual checklists are defined, such that unless all of the component activities have taken place, the project may not be allowed to proceed to the next stage.  Also described here.

Stage gate processes are mostly used by project managers, project management office personnel and business analysts.  Typically each stage will have a checklist that must be followed.  Projects must provide evidence of having performed certain checks, and gain approval before proceeding to the next stage or stage gate.

The Purpose of Stage Gates

The stage gates are intended to prevent projects ideas from becoming prematurely committed without adequate wider consultation across IT and the business.  For example, to proceed from one gate to the next, the project manager will need to show (the PMO) that his project has had the necessary oversight, reviews and collaboration for that particular gate.

According to this PMI article,  gates should address scope change and risk. 

Sometimes gating processes are unsuccessful at delivering the necessary filtering effect (i.e. unready projects proceed, laden with risk) because of the poor effectiveness of the collaboration and scrutiny that takes place at each stage.   Experience has shown that on software projects, measuring functional size is one of the most valuable things that you can do prior to development starting.

More Effective Checks

We advocate using ScopeMaster review at early stages in order to a) improve the quality of thinking around requirements and b) rapidly create, reliable size estimates.  In fact we would go a step further and recommend that companies require the use of ScopeMaster on the early stages of ALL software projects.

Early Risk Removal

By doing this you could improve the completeness of your scope definition, the quality of your requirements and have a reasonably reliable size estimate early on which to base plans and budgets. But most significantly, using ScopeMaster early will lead to you de-risking your projects early.

 

ScopeMaster

Taming software requirements and bringing certainty to software development.

Interpreting software requirements