Project Management

Please login or join to subscribe to this thread

Dear Project Managers, I have a following question in Product Development Process.

linkedin twitter facebook  
avatar
santhosh kumar mohankumar Project Manager| CIRCOR FLOW TECHNOLOGIES Coimbatore, India
Ideally the Development Process will flow like 1. Idea Generation, 2. Idea Evaluation, 3. Concept & Scheduling, 4. Detailed Design and Proto, 5. Verification & Trial Production, 6. Validation & Launch, 6. Post Launch tracking.

Here, i am trying to Combine step 5 & 6 in one stage gate. By doing this, what are all the risks or issues expected by combining 5 & 6?
Sort By:
avatar
Tamer Zeyad Sadiq Assistant Cost Manager| Turner & Townsend Riyadh, Ar Riyad, Saudi Arabia
I think it's a part from Plan-Do-Check-Act cycle!!!!
...
1 reply by Anton Oosthuizen
Aug 30, 2018 1:50 AM
Anton Oosthuizen
...
Product development is not really the same as continues improvement, but it is often the result of it.
avatar
Pawan Rai Senior Project Manager| Axtrics Solution Pvt. Ltd. Ambala, Haryana, India
Do you mean that you would launch the product and verify and validate it at the same time? Though I assume by using the stage gate approach you would first verify and validate it and launch it at the end so all these will be part of just one phase of your project; if so it would be very important to understand how have you planned the entire project?
Are you planning all these gates beforehand or do you go ahead and close one gate and then plan the second?
All these factors play a major role in what risks would be known at a given stage and what still remains as unknown.
when phase gates are used typically detailing for next phase would only be based on phase review of previous phase. If you are at present in any phase that is preceding phase 5 and still thinking about details of phase 5 & 6 then you are actually not following phase-gate process.
avatar
Anton Oosthuizen Senior Business Analyst / Project Manager| Self Employed Pretoria, Gauteng, South Africa
Aug 23, 2018 3:56 AM
Replying to Tamer Zeyad Sadiq
...
I think it's a part from Plan-Do-Check-Act cycle!!!!
Product development is not really the same as continues improvement, but it is often the result of it.
avatar
Anton Oosthuizen Senior Business Analyst / Project Manager| Self Employed Pretoria, Gauteng, South Africa
5 and 6 is actually combined in the SDLC as Testing with the exclusion of launching the product. I would say that it is never a good idea to have your verification/validation (testing) and your release as the same stage gate. Logically it does not make sense since the very thing that will trigger the release stage gate, testing, cannot be in the same phase. That is like each student marking their own paper. The same will hold true for trail run and launch where the whole idea behind a trail is to determine if it is ready for showtime i.e. can we move on to the next gate.
...
1 reply by Susan Marangos
Nov 20, 2020 1:48 PM
Susan Marangos
...
From my experience - something always breaks in the testing no matter how good the code is. These can't be done at the same time in reality you're either going to

1) Release, have untested code (which something won't work) and have to deal with incidents and problems in a live system while you try to finish testing

2) Test and then release which would make it separate steps
avatar
VASUDEV NARAYANAN Program Manager| Pentapolis Foundation Chennai, Tamil Nadu, India
The idea of having a phased approach is to have a bi-directional approach from ideation to launch.

You can combine the phases but you should not unless you have an agreement from your process expert. Do you get the point?

Consider combining the first two phases - 1. The Idea generation, and 2. Idea evaluation. What will be the outcome? A spaghetti product.

Instead of having multiple phases, can I combine all the phases into one-phase? You can answer this better.
avatar
Susan Marangos
Aug 30, 2018 1:56 AM
Replying to Anton Oosthuizen
...
5 and 6 is actually combined in the SDLC as Testing with the exclusion of launching the product. I would say that it is never a good idea to have your verification/validation (testing) and your release as the same stage gate. Logically it does not make sense since the very thing that will trigger the release stage gate, testing, cannot be in the same phase. That is like each student marking their own paper. The same will hold true for trail run and launch where the whole idea behind a trail is to determine if it is ready for showtime i.e. can we move on to the next gate.
From my experience - something always breaks in the testing no matter how good the code is. These can't be done at the same time in reality you're either going to

1) Release, have untested code (which something won't work) and have to deal with incidents and problems in a live system while you try to finish testing

2) Test and then release which would make it separate steps
avatar
Wendy English Senior Project Manager| Humphrey Products Kalamazoo, Mi, United States
Releasing without first confirming the product you are releasing meets the goals of the project may put you at risk of
1) time overrun
2) budget overrun
3) faulty product at launch

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Critics can't even make music by rubbing their back legs together."

- Mel Brooks

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters