Before beginning a discussion of how to make the Go Decision in Project Management, there needs to be a discussion regarding what, when and why does management need to make this decision.
Why can’t we accept all projects for our organization?
Just what is the Project Go Decision as defined by the Project Management Body of Knowledge (PMBOK)?
As defined by the PMBOK it is stage one of a project that covers project formulation, feasibility studies, strategy design and approval. If these factors are not analyzed by an organization there is a very high percentage that they may end up filing for chapter 11, because they tried to be everything to everyone and, as we all know everyone has limited resources. If management does not take the time to analyze the project they end up with a failed project, or a never ending project.
It follows that many projects never make it to the Planning Process. But once a Go Decision is made, the Project Manager is selected and the project officially starts. It is important to note that in most cases executive management is making the Go Decision.
Note: On most small to mid-size projects, the Project Manager is not chosen until the start of the Planning Process. On very large complex projects, it is recommended that the Project Manager be selected as part of the investigation team, or even in charge of the investigation team.