项目立项报告模板.doc

Project Charter TemplatePurpose provide the Project Manager with the authority to apply organizational resources to project activities align customer and project expectations establish the purpose of a project demonstrate the Organizational Leadership Teams commitment to the project Intended Audience management stakeholders, customers other staff in the organization Components1. Executive SummaryWrite a few paragraphs describing at a high level the key elements of the project that are detailed throughout the charter. 2. Strategic Alignment1. Specific Strategic InitiativesAnswer the questions: What university initiatives does this project support? What are the expected outcomes or benefits (impact on processes, systems, people, organizations)? 2. Project StakeholdersWho are the customers and sponsors? 3. Project Definition1. MissionState the purpose of the project. 2. ObjectivesClearly state 1-2 project objectives that are concise, verifiable, feasible, and measurable. 3. Scope/Major DeliverablesThe project deliverables define the products/services that are produced by the project and clearly state what is not produced by the project. Deliverables not included may be those constructed in a later project phase, or those to be constructed by another project. Be as clear as possible in defining the project deliverables. Clear and obtainable deliverables set the direction of the project and eliminate confusion about what work is performed and what products/services are delivered. 4. Quality SpecificationsDescribe the product or service performance criteria from a customer perspective. 5. AssumptionsProject assumptions clarify gray areas in the project scope. Any known assumptions that have been made regarding the project that may influence this agreement should be noted. Note: Assumptions are made to fill knowledge gaps; they may later prove to be incorrect and can have a significant impact on the project. List only those assumptions that have a reasonable chance of occurring. 6. ConstraintsList any known constraints imposed by the environment or by management. Typical constraints may include fixed budget; limited resources; imposed interim and/or end dates; predetermined software systems and packages; and other predetermined solutions. 7. Human Resource RequirementsDefine the project teams organizations, roles and responsibility requirements. Provide a description of major participants including the various internal and external organizations. Role Responsibility Time Commitment Duration Source (internal, external) 8. If necessary, identify training requirements and begin to develop the Project Team Training Plan to be finalized after detailed planning. Training includes: Technical training relevant to the project domain (e.g. IT development, procurement, logistics, systems training, etc.) Team Training (e.g. team building, team effectiveness, team performance, consensus decision making, etc.) Project Management (e.g. project management concepts) Procedures/user manuals, training liaison, etc. needed for/by business users. 9. Material/Equipment ProcurementInclude information regarding the lease or procurement of required equipment and materials. 10. MilestonesDefine the milestone schedule of the project, integrating three key elements: deliverables, due date or duration, critical dependencies. 11. Preliminary Budget/Cost EstimateThis estimate is prepared at a gross level for the project charter. Estimates are typically prepared for: the duration of the project the human resource requirements in terns of numbers and types of skills required on the team the cost of performing the work defined in the project charter the material and equipment resources in terms of quantity and duration. Decisions to proceed with the project could be based on this information. Therefore, it is important to ensure that it is as accurate and realistic as possible. The objective here is to gain approval of the Project Charter as quickly as possible without developing project details. As the project traverses through the stages outlined in the methodology, more information will be known and unpredictability will be reduced. Therefore, at the end of each stage and after detailed planning for the next phase, the cost/benefit analysis is updated and the information communicated as needed. Good estimates require: time and focus historical information or previous experience multiple, consistent estimating methods knowledge of the work Costs are divided into three types: 9. Capital Items: associated with the procurement of assets that are capitalizable such as hardware and software 10. Expense Items: associated with operating expenses, material, travel, training, supplies, books, copying, printing, etc. 11. Labor: associated with the total time team members work on a project based on an hourly rate for each skill set or the actual salary of the team members 12. Major Overall RisksIdentify and assess known project risks. Risk Event Probability Impact Duration Risk Strategy 13. Information RequirementsDescribe the system of communications and the project performance documentation that will be provided to the various stakeholders. Stakeholder Report Requirements Frequency 4. Related Products and DeliverablesDocument known project dependencies with other groups within or outside of the organization. Deliverable, Event, Support Individual or Group Responsible Team Owner 5. ApprovalsUse this section to capture approval signatures from proje