02_Project Charter 项目批准书

鉴定结项审批书范文
英文回答：
Certificate of Project Completion.
This document certifies that the following project has been successfully completed:
Project Name: [Project Name]
Project Number: [Project Number]
Project Manager: [Project Manager]
Date Completed: [Date Completed]
The project was completed on time and within budget. All project objectives were met, and the project deliverables were delivered to the client's satisfaction.
The project team would like to thank the client for their support and cooperation throughout the project.
中文回答：
结项审批书。

本文件证明以下项目已成功完成：
项目名称：
项目编号：
项目经理：
完成日期：
该项目按时按预算完成。

所有项目目标均已实现，项目成果已按客户要求交付。

项目团队感谢客户在整个项目期间的支持与合作。

鉴定意见：
经审查，本项目已按合同要求完成，符合验收条件。

同意结项。

鉴定人：
日期：。

Project Plan/Project CharterProject NumberASSIGN A NUMBER.Project Or Sub-Project NameApplications Delivery MethodologyBackgroundNAME OF CLIENT must dramatically improve its ability to delivery business applications in a timely, cost-effective, flexible and quality manner. Specific program goals include achievement of at least an order of magnitude productivity improvement.ScopeTwelve functional objectives have been identified for project completion:1. Provide identifiable and measurable improvements to the applicationsdelivery process. Specific measures of improvement will be identified as partof concept validation.2. Central repository of delivery routes customized to capture CLIENT’S bestpractices implemented.3. Processes in place to support project managers in the use of the uniform andproven best practices to generate project plans.4. Support of the enterprise CMM/SEI objectives.5. Time, cost and quality metrics and effort estimation models implemented.6. Consistent use of the methodology for applications delivery.7. Continuous process improvement infrastructure defined and implemented.8. Risk driven project management implemented.9. Process library delivery routes controlled from the process librarianworkstation.10. Project management automated and controlled from the project manager’sworkstation.11. Knowledge transfer to CLIENT completed.12. Sustaining organization defined and implemented.Concept DefinitionThe concept is that a methodology will dramatically improve CLIENT’s ability to deliver business applications in a timely, cost-effective, flexible, and quality manner. This concept will be achieved through:• A proactively managed applications delivery environment;•Process, technology, organization, people, and leadership factors all planned and integrated;• A very high degree of reuse through employment and enforcement of NAME OF METHODOLOGY TOOL, standards, specifications, and reusable frameworks and components designed for flexibility; and•An ongoing preventive maintenance program.Areas of ImpactThe IS project manager and teams will be the primary areas impacted by this project. During the deployment (concept validation, full-scale development, and implementation) phases, the methodology project will fund for activities relating to deployment.•Pathfinder projects will provide resources for training, to support customization of the process tool product, participate in project meetings, and support assessments.Specific resource requirements for each project will be determined at project start-up.•Limited workstation services support will be required to support tool implementation.RisksRisk Area Assessment Impact Mitigation Leadership,Support and Buy-In HighProject requires support byIS Department Heads for anenterprise infrastructuresolution.Dedicated changemanagement effort.Staffing Medium Success of project dependson ability to staff withcredible experience in thetechnical areas.Use of 3rd party vendors tobuild internal expertise;staffing assessment at eachproject review.Cost Medium We developed an earlyestimate of 98 and 99 costs.However, we do not yet havea full understanding ofsustained costs.Develop a total life cycle costestimate during conceptvalidation as part of themilestone decision.Schedule Medium Current industry practicesindicate 18-36 months wererequired to institute amethodology.Introduction of methodologyinto CLIENT based on “pull”from applications deliveryareas.Scope Low Successful completion ofconcept validation will resultin a client-wideimplementation.-Quality Unknown This risk factor will dependon the results of conceptvalidation.Continue to understand ISdepartmental requirements forrepeatable processes andrigor.Assumptions1. The methodology will be piloted using pathfinder projects that represent typicalCLIENT applications delivery efforts.2. Methodology project members will participate in the pathfinder projects to gainknowledge of the effectiveness of the methodology for enterprise use.3. The initial pathfinder projects will use NAME/DESCRIPTION of approach forimplementation and deployment.4. The deployment will run through the end of YEAR.5. LIST ANY OTHER ASSUMPTIONS HERE.Constraints1. Concept validation will run through MONTH, YEAR and is budgeted for $AMOUNT.2. YEAR budget is $AMOUNT.3. Late selection of concept validation pathfinder projects may constrain the amount ofquantitative information to support the full-scale development milestone decision.Implementation ApproachThe implementation will occur from WHEN through WHEN with the following phase points currently planned:1. Concept validation through MONTH/YEAR at a cost of $AMOUNT. During this phase,the methodology will be implemented on NUMBER OF projects WHERE. Overall implementation planning will also be completed during this phase.2. DESCRIBE FIRST FULL-SCALE DEPLOYMENT PHASE AND TIMEFRAME.3. DESCRIBE SECOND FULL-SCALE DEPLOYMENT PHASE AND TIMEFRAME.4. Implementation through the end of YEAR. Implementation on additional projects,completions of knowledge transfer to CLIENT, and activation of the sustaining organization.The project RoadMap will describe the overall project implementation plan, including work packages and deliverables for each year. The RoadMap also defines the overall project completion goals and the specific objectives set for each year of the implementation. Specific implementation project plans for each approved phase will be developed at the milestone decision points.Functional RequirementsThe following table reflects the requirements this project will solve by phase. A specific project plan will be developed at the start of each phase and will provide the specific work packages required to satisfy the requirements.Concept Validation - YEAR Full Scale Deployment - YEAR Implementation - YEAR1. CLIENT proof of conceptpathfinder projectsidentified and initiated. 2. Pathfinder project lessonslearned gathered andanalyzed.3. Initial CLIENT pathfinderproject staff trained inNAME OFMETHODOLOGY TOOLmethods.4. Training improvementsidentified for methods andtool.5. Initial technicalinfrastructure defined anddeployed.6. Pathfinder project teams 1. Forty percent of CLIENT ITSolutions Delivery stafftrained.2. Technical infrastructurerefined.3. Training programestablished.4. Project estimating &tracking improved.5. Interaction withimplementation of new toolset managed.6. Projects planned &managed jointly bybusiness & IT projectmanagers.7. CLIENT metrics definitions1. TBD percent of CLIENT ITSolutions Delivery stafftrained.2. One hundred percent oftraining responsibilityassumed by CLIENT.3. Integration with externalinitiatives completed.4. Technical infrastructurerefined.5. CLIENT best practices fromlessons learnedincorporated intomethodology.6. Repository of best practices-reusable templates,deliverables, and methodsestablished.Concept Validation - YEAR Full Scale Deployment - YEAR Implementation - YEARavailable to seed newprojects.7. Roadmap approachapproved by SteeringCommittee.8. Process librarymanagement andenhancementinfrastructure establishedfor pathfinder routes.9. Process improvementmetrics for time, cost, andquality established for CVand identified for FSD &Implementation.10. Policies, standards, andcompliance criteriaidentified for methodologyinstitutionalization.11. FSD phase defined andplanned.incorporated in NAME OFMETHODOLOGY TOOL8. Continuous processimprovement processestablished.9. Standardized processesand methods defined withlimited use.10. Sixty percent of classroomtraining responsibilityassumed by CLIENT.7. Application productivityincreased.8. System quality improved by(Percentage TBD)9. Application delivery cycletime reduced.Key People•Program Sponsor: NAME, TITLE•Methodology Project Sponsor: NAME•Program Manager: NAME•Methodology Project Lead: NAME ApprovedNAME, Program Manager Date。

项目任务书(project charter)又名：任务说明书(mission statement)➢概述项目任务书是对一个改进项目审定和定义的文档。

➢适用场合·当一个项目开始时；·只要有人需要关于项目的信息或者目的阐述、范围、时机、状况等；·评估时，确保项目适当地集中且准时，更新目前进展任务书；·当项目过程中所得的信息表明需要变更任务书时。

➢实施步骤1项目的支持者（发起并且支持项目的管理成员）和项目小组领队在项目开始时共同起草任务书。

许多企业都有标准的格式。

这里是一些基本的元素，下面的注释和问题可以帮你完成表格。

项目题目报告以及最佳实践中的该项目如何命名？过程名以及产品或服务影响什么功能和企业的输出将成为项目焦点？问题描述目前过程、产品或服务出了什么问题？目标／目的希望有什么改进和结果？根据用来判断成功的过程测量指标阐述结果。

范围过程的哪些方面需要包含进去，哪些方面不需要包含进去？过程的起始点和结束点各是什么？商务方面过程的重要之处是什么？目前的不良质量的成本是什么？该项目有哪些对财务方面（成本节约、利润增长、成本避免）的影响？哪些将影响外部顾客？项目起始日项目任务书所定义的日期。

目标完成日基于项目复杂度、假期、工作量、旅游以及顾客合约要求等方面的估计。

预期里程碑日期检验、描述、客户参观等人员列出名单、角色以及联系信息：·项目发起人·项目领导·小组成员·小组督导者·专业技术人员·其他的过程或者项目专家·其他重要的利益相关者签名和日期准备和批准签名、日期以及修正日期。

2任务书可以由管理层进行检查和批准。

3在早期定义顾客需求、伸展宽度问题以及建立测量系统的过程中，项目逐渐得到更准确的定义，应该检查、修订并重新审批任务书。

➢示例Medrad的财务人员想要减少处理货运清单所需的工作量，以使人们可以做更具增值性的工作，减少临时职位，也可以为公司未来的成长做准备。

签字：日期：
10-项目总结表
项目总结表
Project Overviews
一、项目基本情况Project Basic Info.
项目名称Project name：
项目编号project code：
制作人Prepared by
审核人reviewed by：
项目负责人project leader：?
制作日期data：
审核人reviewed by：
项目负责人project leader：?
制作日期data：
二、当前任务状态（简要描述任务进展情况）
关键任务
状态指示
状态描述
三、本周期内的主要活动（对本周期内的主要交付物进行总结）
四、下一汇报周期内的活动计划（描述活动需要与项目计划和WBS相对应）
五、财务状况
六、上期遗留问题的处理（说明上一个汇报周期内问题的处理意见和处理结果）
制作日期data：
二、历史变更记录（按时间顺序记录项目以往的每一次变更情况）
序号
变更时间
涉及项目任务
变更要点
变更理由
申请人
审批人
三、请求变更信息
受影响的基准计划
1、进度计划
2、费用计划
3、资源计划
是否需要成本/进度影响分析：
对成本的影响
对进度的影响
对资源的影响
申请人签字
申请日期
五、审批结果
审批意见：
四、发放材料（列出会议讨论的所有项目资料）
五、发言记录（记录发言人的观点、意见和建议）
六、会议决议（说明会议结论）
七、会议纪要发放范围
08-项目状态报告表
项目状态报告表
一、项目基本情况Project Basic Info.