COMINDWORK: Talk: How To Prepare Project Initiation Document
Among the issues that need to be addressed in the project initiation document, some are required and some are optional. Here are some common things that should be taken into consideration when putting up such documents: - Problem/opportunity statement (required): What is the problem or opportunity of the project? This section should provide background on the factors that led to the project and, where appropriate, some history of what has been attempted in the past.
- Scope definition (required): What are the quantifiable characteristics or end results to be achieved? The scope definition should respond to the problem or to the opportunity. The end product might be a specified product, process, or service.
- Completion criteria (required): What needs to be done? How will it be measured in the most objective terms? How will we know when we're finished? The completion criteria should indicate whether it is the design, the prototype, or a complete working product, system, or process that is the goal of the project. Consequently, this completion criterion or standard of performance needs to be quantifiable. The objective is to sate the goal clearly so that there wouldn't be any questions upon project completion
- Assumptions (optional): What has been assumed? Is everyone aware of these assumptions? Remember that what you, the project manager, assume will form the basis upon which to build the project plans. If the other stakeholders, particularly the client, have not made the same assumptions, there will be a major difference in expectations.
- Risk (required): What are the risks of doing or not doing this project? It can be a detailed mathematical presentation with which to project the financial and other benefits. Or you can provide a business analysis of the major risks and rewards that provide the basis for deciding whether it is worth to proceed with the project.
- Resource requirements (optional): What resources will be required? This section should alert particular areas of the organization that their staff members will be required to support this project. You may also want to announce whether you will need any special or unusual resources for the project. Do not make definitive specifications at this point since you do not have enough information to plan. Rather, include a generic statement of skill mixes that will be eventually requested.
- Constraints (optional): Are there any special constraints imposed upon the project? These could be environmental factors such as terrain, weather conditions, or Environmental Protection Agency requirements. There may be constraints imposed by equipment, technology, or chronological limitations to be considered. Get them out on the table at the beginning of the project so that you will have the opportunity to re-evaluate and pursue alternative solutions.
Remember that Comindwork integratred wiki system is ideal for creating and managing all kinds of project documents as wiki pages weather it is PID (Project Initiations Documents), project charter, risk analysis or any other.
No comments yet, be the first to comment
|
|