Table of Contents
Gate Review Method
In ESW, we use the Phase-Gate Review Method to structure projects and provide them resources. This is actually a common review practice in businesses, so you might come across it later on. In business, it’s used to evaluate risk and lead to profitable product deployment. In ESW, it’s used to help your team keep track of where it is, where it needs to go and how it can get there.
Below is what a standard system might look like in a professional setting.
Figure 1- Typical Phase-Gate Review System for Product Development
The phases represent where projects are in development and what end-goals they should be working toward. Once they achieve the phase’s end-goal, they enter the “gate” where their work is evaluated. At the evaluation, the team may be passed into the next stage, asked for clarifications and made aware of problems that they should work out, or both the Board of Project Directors and the project team may mutually agree that the project cannot continue any further.
Our phase-gate system is similar, but we use different phases, and the purpose of the gates aren’t to evaluate profitability, but rather to help keep projects moving along a development path, provide projects with resources and advice, and to help them make sure they’re as sustainable and safe as possible. The nature of the gate-review also depends on the scope, complexity and overall difficulty of the project. For example, some projects may take longer to pass a gate or even have to revisit the development phase if the project design is not comprehensive enough.
Passing a Phase:
We have created a series of deliverables for projects to utilize during each phase to ensure that they finish all of the necessary details to pass a phase. The deliverables are linked to in each "What to Submit" section of each Phase and should be used as a template for your project's own work.