My company is developing projects. I’m trying to come up with a stage gate process where all deliverables are defined and the conditions of the deliverables are defined at each gate approval. Saving Changes...
You can find a lot of information online about different stage gate/phase gate approaches. Lean Six Sigma is one approach, but it can be a bit much if people aren't used to rigorous approaches. I've heard some noise about agile stage gates, but haven't looked into it, yet.
We tried implementing a stage gate approach at my last employer, when we stood up a new PMO. The stage/phase reviews weren't attended well, initially. We had some larger projects where we had successful reviews, but we started getting less formal on smaller projects and had other projects with overlapping phases where formal reviews didn't make sense.
I don't know the details of your situation, but you might want to have some sort of scaled approach, unless all of your projects require the same level of rigor and scrutiny. Saving Changes...
If you search google for DoD gated process or IEEE gated process, you will find multiple resources. Often the gates are required on projects of significant size, not on everything. The basic gates themselves are often relatively straightforward. The detailed criteria for whether or not the project can pass the gate vary by company or government agency and may be confidential OPAs. Saving Changes...
Vijay SuryavanshiProject Manager - Engineering| RECARO Aircraft SeatingPlantation, Fl, United States
What kind of company is yours ? Understand it is development project. For research and development project it is important you follow the phase gate process. And often in aviation it is followed. Usually the sponsors define the deliverables or you can work with them to develop it. Even though you follow the phase gate process, it is important you know which of the phases are crucial with major milestones. A lot of employees are hesitant to follow each gate process and sometimes it is impractical. This because the actual work ends up over lapping. However, why the phase gate becomes important in development work is it gives the sponsors or upper management review internally and make a "GO" or a "NO GO" decision. Which means if there is enough progress that you can build on each phase, then you move on to the next phase. (There will be dependency mostly linear. It won't make sense if first. ) A " NO GO" usually means you have to revisit your phase and fix the issues to complete all delvierables before moving on to next phase. Else if there is not enough development where all deliverables (major and important one that are required for next stage) in that phase are met then the project is reevaluated and sometimes discarded. Spending too much time where you don't get ROI without further development makes no sense. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
What kind of company is yours and how is going to define the deliverables? If not, you can define them by gathering requirements, phase wise processes and define difficulties and major milestones, avoid overlapping. ensure all accepted deliverables are closed phase by phase, before moving forward to next phase. conduct retrospectives for every phase. Saving Changes...
"When I examine myself and my methods of thought, I come to the conclusion that the gift of fantasy has meant more to me than my talent for absorbing positive knowledge."
Community Champion
