The Stage Gate process: A powerful project management concept
From apppm
(Difference between revisions)
|
|
| (5 intermediate revisions by one user not shown) |
| Line 1: |
Line 1: |
| − | ''Developed by DTU student, Lillian Nygaard''
| |
| | | | |
| − |
| |
| − | =Abstract=
| |
| − | When it comes to achieving a successful project – The main foundation is efficient project management. A simple method to secure this When it comes to achieving a successful project – The main foundation is efficient project management. A simple method to secure this is by executing projects through a Stage-Gate process. The Stage-Gate process is method that guides a project from discovery to launch in an organized and efficient manner. It involves breaking down the project into stages which are separated by gates. The gates are used to decide whether or not the project should proceed into the following stage. The Stage Gate process was developed by Dr. Robert G. Cooper and presented in the book 'Winning At New Products' in 1986 <ref> Cooper, R.G, 1986, Winning At New Products, Addison Wesley, ISBN-10: 0201136651</ref>. The process is implemented by more than 80% of the companies in North America and the implementation of the process worldwide is growing as companies are pursuing to develop their innovation competences. <ref>S. J. Edgett, Idea‐to‐Launch (Stage-Gate®) Model: An Overview,</ref> The Stage Gate process include five stages that the project is proceeding through. Each stage is created to acquire information for the purpose of the project to proceed into the next stage. The five stages are characterized by specific activities that must be accomplished within each stage. To expedite the project’s progression towards the next stage, the activities are completed in parallel in the different departments within each stage. These activities are intended to acquire knowledge about the project while increasingly reducing ambiguity and risk. The outcome of the activities becomes the foundation of deciding whether to continue to invest in the projects which also is referred to as the gates.
| |
| − |
| |
| − |
| |
| − | =Big Idea=
| |
| − |
| |
| − | describe the tool, concept or theory and explain its
| |
| − | purpose. The section should reflect the current state of the art on the
| |
| − | topic
| |
| − |
| |
| − | =Application=
| |
| − |
| |
| − |
| |
| − | provide guidance on how to use the tool, concept or
| |
| − | theory and when it is applicable
| |
| − |
| |
| − | =Limitaions=
| |
| − |
| |
| − |
| |
| − | critically reflect on the tool/concept/theory. When
| |
| − | possible, substantiate your claims with literature
| |
| − |
| |
| − | =Annotated bibliography=
| |
| − |
| |
| − |
| |
| − | Provide key references (3-10), where a
| |
| − | reader can find additional information on the subject.
| |
| − |
| |
| − |
| |
| − | =References=
| |
| − |
| |
| − | <references />
| |
Latest revision as of 22:44, 11 February 2023
