Comments on: Conducting Successful Gate Meetings http://www.pmhut.com/conducting-successful-gate-meetings Mon, 21 May 2012 14:54:24 +0000 http://wordpress.org/?v=abc hourly 1 By: Mukesh http://www.pmhut.com/conducting-successful-gate-meetings/comment-page-1#comment-20496 Mukesh Wed, 28 Apr 2010 06:21:36 +0000 http://www.pmhut.com/conducting-successful-gate-meetings#comment-20496 Great Article on Stage gate meeting and its relevance and great insights we are also in process on learining and taking advantage on process in our organisation and found this very helpful Regards Mukesh Great Article on Stage gate meeting and its relevance and great insights

we are also in process on learining and taking advantage on process in our organisation and found this very helpful

Regards
Mukesh

]]> By: CMM and Project Quality Management - PM Hut http://www.pmhut.com/conducting-successful-gate-meetings/comment-page-1#comment-19757 CMM and Project Quality Management - PM Hut Sun, 04 Apr 2010 18:44:35 +0000 http://www.pmhut.com/conducting-successful-gate-meetings#comment-19757 [...] SQA personnel. These may come through special meetings scheduled for the purpose or regular gate review meetings. The Gate Review meeting that marks the transition from build to deployment will usually be [...] [...] SQA personnel. These may come through special meetings scheduled for the purpose or regular gate review meetings. The Gate Review meeting that marks the transition from build to deployment will usually be [...]

]]> By: Ahad L. Amdani http://www.pmhut.com/conducting-successful-gate-meetings/comment-page-1#comment-968 Ahad L. Amdani Tue, 18 Nov 2008 21:02:27 +0000 http://www.pmhut.com/conducting-successful-gate-meetings#comment-968 Dave, I'm glad I've read this article - specifically because it made me realize a couple of additional points with regards to stage gates. Primarily, the gate meetings themselves - why they should be held, and when they should be held during your projects. The parts dealing with who should attend and how to run the meetings are more political in nature and I feel are different/unique per situation. > Gate meetings also serve the purpose of validating the Business Case. As the project’s scope, budget, and schedule change throughout its life cycle, your Business Case will change. Hadn't considered this aspect. I realize that the project evolves, the customers evolve and the business relationship evolves, so we would have to update documentation, but I hadn't considered the need to update the business case for the project. We usually work with technical writers and they take care of this for us - but it's definately something an independant consultant or small team should take into account. > The Business Case may also be changed by circumstances outside the span of your control such as changes in the market place. The Gate Meeting is your opportunity to have the updated Business Case validated by your project’s executive sponsors. Yes, another great effect of updating your business case would be its re-validation against the market. > The second [gate meeting] is critical because this is the meeting where the customer will formally accept the products of the project. It should drive any formal sign offs and final payments that conclude the project. I've always preached and practiced holding what I now call gate meetings many times over the development cycle of a project, but I don't think I've ever held one before customer sign-off. We had small reviews to ensure whether or not all of the features had been fully completed and tested out, but never to evaluate whether the business case still stood, whether or not to cut the project off or restructure it, etc. I'll have to try it out and see if the sponsors / clients would be interested in changes from what we had originally considered the "final release." I think mostly because since we follow the Stage Gate process, we feel that things are aligned towards a successful completion assuming all coding and functionality are completed for the fully evolved project. But always room to try and it costs no more than a day of work. Dave,

I’m glad I’ve read this article - specifically because it made me realize a couple of additional points with regards to stage gates.

Primarily, the gate meetings themselves - why they should be held, and when they should be held during your projects.

The parts dealing with who should attend and how to run the meetings are more political in nature and I feel are different/unique per situation.

> Gate meetings also serve the purpose of validating the Business Case. As the project’s scope, budget, and schedule change throughout its life cycle, your Business Case will change.

Hadn’t considered this aspect. I realize that the project evolves, the customers evolve and the business relationship evolves, so we would have to update documentation, but I hadn’t considered the need to update the business case for the project. We usually work with technical writers and they take care of this for us - but it’s definately something an independant consultant or small team should take into account.

> The Business Case may also be changed by circumstances outside the span of your control such as changes in the market place. The Gate Meeting is your opportunity to have the updated Business Case validated by your project’s executive sponsors.

Yes, another great effect of updating your business case would be its re-validation against the market.

> The second [gate meeting] is critical because this is the meeting where the customer will formally accept the products of the project. It should drive any formal sign offs and final payments that conclude the project.

I’ve always preached and practiced holding what I now call gate meetings many times over the development cycle of a project, but I don’t think I’ve ever held one before customer sign-off. We had small reviews to ensure whether or not all of the features had been fully completed and tested out, but never to evaluate whether the business case still stood, whether or not to cut the project off or restructure it, etc. I’ll have to try it out and see if the sponsors / clients would be interested in changes from what we had originally considered the “final release.” I think mostly because since we follow the Stage Gate process, we feel that things are aligned towards a successful completion assuming all coding and functionality are completed for the fully evolved project. But always room to try and it costs no more than a day of work.

]]>