by Renaud Anjoran
In the previous article we mentioned that there should be a Stage Gate Review meeting between each of the development phases. Here we will look at the guidelines for these Stage Gate Reviews.
This review meeting is commonly referred to as the Gate which acts as stop/go virtual barrier between phases. These gates serve as quality control check points on all of the information and data generated throughout the preceding development phase.
There is a structure that should be followed during these gate reviews and it is important to follow a structure. Without a structure and the discipline to follow a structure, the gate part of the stage gate process becomes the weakest part of the process and inevitably poor decisions are made or projects are allowed to move onto the next phase that in truth should either be killed off or reverted back through the preceding phase for additional work.
It has been stated a number of times that this process should act as a funnel and not a tunnel and it is the gates that do the filtering and funnelling.
The structure of each of the Gates is similar throughout the whole process so we will just show a guideline to the basic structure.
The deliverables are a set of pre-determined criteria that need to be delivered for review during the gate review meeting; these deliverables should include documentation, data, in some cases physical samples and models. All deliverables regardless of what shape or form they are in should be relevant to the preceding phase and this is what is reviewed during the gate meetings.
Criteria against which the project is judged, this includes different levels from the ‘must meet’ to the ‘should meet’ down to the ‘ideal to have at this stage’. Each gate should have its own checklist and this is where the process is unique as every product will have its own unique set of features and attributes that need to be met.
The output is ultimately the stop or go decision for the project. This can obviously include ‘put on hold’ and the ‘revert back the preceding phase’ which allows further work to be carried out in order for the project to be resubmitted to the review gate.
If the project gets the ‘go’ the project can then move into the next development phase and part of the output would be a plan to shows company financial support and commitment, which include resources, timescales for the next phase and the set of deliverables that must be met during the next phase and which will be used at the next gate review to judge the project against.
At each of the gate reviews there should be key personnel as shown above, but collectively they are known as the ‘gatekeepers’.
Gatekeeper RULES of ORDER need to be established and enforced (by review meeting chairman). These rules are shown below: