 | Requirements Gathering: |
| | This involves confirming the business objectives, and documenting the business and functional requirements (may also include high level technical requirements), as well as providing high level assessment of current project management practices and proficiencies. |
| Prototype: |
| | This involves setting up a “Prototype” to demonstrate capabilities & limitations of system (test adherence to requirements & fitness for use specific to your organization & business expectations) - includes completion of analysis and production of business case or recommendations report. |
| Project Definition and Initiation: |
| | Bringing the business requirements and the knowledge gained from the prototype together to finalize an implementation strategy. This includes establishing a pilot area and deployment strategy; confirming the project structure and sponsorship; finalizing the project scope and producing the project schedule and budget along with the rest of the project plan materials. |
| System & Process Design / Build: |
| | This involves assessing current project management environment, gaining an understanding of the people that will be using the system, how they will be using it, and their current level of skill (experience + product knowledge). Assessing current PM processes, procedures and forms/templates and defining the ‘to be’ processes will also be done at this point. |
| Pilot Program: |
| | This pilot must be limited to a logical and manageable group and must address all the functionality required in the enterprise wide version. |
| Roll Out & Training: |
| | This involves the training and roll-out of the solution to all identified participants as per the deployment strategy identified in Phase 3. |
| Support: |
| | The project team provides support from the pilot until a set period of time after the completion of the roll out. This also includes working with the operational groups to transition ongoing management of support from the project team to the operations
group(s). |
