项目管理计划模文档新板(英文)

合集下载

项目管理PMP精要(中英文对照)

ESSENCE OF PMBOK & PMP EXAMPMBOK及PMP考试精要(考试串讲教材)PROJECT MANAGEMENT KNOWLEDGE AREAS项目管理知识体系 (2)PROJECT LIFE CYCLE / PROJECT MANAGEMENT PROCESS GROUPS项目生命周期及过程组 (10)SCOPE范围管理 (10)HUMAN RESOURCE人力资源管理 (11)COMMUNICATIONS沟通管理 (14)TIME时间管理 (16)COST成本管理 (17)RISK风险管理 (20)QUALITY质量管理 (22)PROCUREMENT采购管理 (22)INTEGRATION整体管理 (19)PROFESSIONAL RESPONSIBILITIES职业道德 (19)POSSIBLE EXAM QUESTIONS考点 (20)Project Scope Management项目范围管理- processes required to ensure that the project includes only the work required to complete the project successfully.此过程必须确保项目只包括能保证项目成功完成的工作Management by Objective (MBO)基于目标的管理–determining company’s objective and how the project fits into them. MBO focuses on the goals of an activity rather than the activity itself (manager is responsible for results rather than performing certain activities)决定公司目标及项目如何满足该目标。

项目管理PMP精要（中英文对照）

ESSENCE OF PMBOK & PMP EXAM 考试串讲教材))PMBOK及PMP考试精要考试精要((考试串讲教材PROJECT MANAGEMENT KNOWLEDGE AREAS项目管理知识体系 (2)项目生命周期及过程组 (10)PROJECT LIFE CYCLE / PROJECT MANAGEMENT PROCESS GROUPSSCOPE范围管理 (10)HUMAN RESOURCE人力资源管理 (11)COMMUNICATIONS沟通管理 (14)TIME时间管理 (16)COST成本管理 (17)RISK风险管理 (20)QUALITY质量管理 (22)PROCUREMENT采购管理 (22)INTEGRATION整体管理 (19)PROFESSIONAL RESPONSIBILITIES职业道德 (19)POSSIBLE EXAM QUESTIONS考点 (20)1 PROJECT MANAGEMENT KNOWLEDGE AREAS项目管理知识体系Knowledge Areas知识体系Primary Inputs输入Tools & Techniques工具及技术Primary Outputs输出INTEGRATION整体整体制定项目章程 Develop Project Charter 1.合同(如果适用) Contract(When applicable) 2.项目工作说明书 Project statement of work 3.事业环境因素 Enterprise environmental factors 4.组织过程资产组织过程资产 Organizational process assets 1.项目选择方法 Project selection methods 2.项目管理方法论项目管理方法论 Project management methodology 3.项目管理信息系统项目管理信息系统 Project management information system 4.专家判断专家判断 Expert judgment 1.项目章程 Project charter 制定项目初步范围说明书制定项目初步范围说明书 1.项目章程 Project charter 2.项目工作说明书 Project statement of work 3.事业环境因素 Enterprise environmental factors 4.组织过程资产 Organizational process assets 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 3.专家判断 Expert judgment 1.项目初步范围说明书项目初步范围说明书Preliminary project scope statement 制定项目管理计划制定项目管理计划 Develop Project management Plan 1.项目初步范围说明书 Preliminary project scope statement 2.项目管理各过程 Project management processes 3.事业环境因素 Enterprise environmental factors 4.组织过程生产 Organizational process assets 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 3.专家判断 Expert judgment 1.项目管理计划 Progece management plan 指导与管理项目执行 Direct and Manage Project Execution 1.项目管理计划 Progece management plan 2.批准的纠正措施 Approved corrective actions 3.批准的预防措施 Approved preventive actions 4.批准的变更申请 Approved change requests 5.批准的缺陷补救 Approved defect repair 6.确认的缺陷补救 Validated defect repair 7.行政收尾程序 Administrative closure procedure 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 1.可交付成果 Deliverables 2.请求的变更 Requested changes 3.实施的变更请求 Implementde change requests 4.实施的纠正措施 Implementde corrective actions 5.实施的预防措施 Implementde preventive actions 6.实施的缺陷补救 Implementde defect repair 7.工作绩效信息 Work performance information 监控项目工作 Monitor and Control Project Work 1.项目管理计划 Progece management plan 2. 工作绩效信息 Work performance information 3.否决的变更请求否决的变更请求 Rejected change requests 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 3.实现价值技术实现价值技术 Eamed value technique(EVT) 4.专家判断 Expert judgment 1.推荐的纠正措施推荐的纠正措施Recommended corrective action 2.推荐的预防措施推荐的预防措施推荐的预防措施Recommended preventive action 3.预测预测 Forecasts 4.推荐的缺陷补救推荐的缺陷补救Recommended defect repair 5.请求的变更 Requested changes 整体变更控制 Integrated Change Control 1.项目管理计划项目管理计划 Progece management plan 2.请求的变更请求的变更 Requested changes 3.工作绩效信息工作绩效信息 Work performance information 4.推荐的纠正措施 Recommended corrective action 5.推荐的预防措施推荐的预防措施 Recommended preventive action 6.推荐的缺陷补救推荐的缺陷补救 Recommended defect repair 7.可交付成果可交付成果 Deliverables 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 3.专家判断专家判断 Expert judgment 1.批准的变更申请 Approved change requests 2.否决的变更请求 Rejected change requests 3.项目管理计划(更新) Project management plan(updates) 4.项目范围说明书(更新) Project scope statement(updates) 5.批准的纠正措施 Approved corrective actions 6.批准的预防措施 Approved preventive actions 7.批准的缺陷补救 Approved defect repair 8.确认的缺陷补救 Validated defect repair 9.可交付成果 Deliverables 项目收尾 Close Project 1.项目管理计划 Progece management plan 2.合同文件 Contract documentation 3.事业环境因素 Enterprise environmental factors 4.组织过程资产组织过程资产 Organizational process assets 5.工作绩效信息工作绩效信息 Work performance 1.项目管理方法系 Project management methodology 2.项目管理信息系统 Project management information system 3.专家判断专家判断 Expert judgment 1.行政收尾程序 Administrative closure procedure 2.合同收尾程序合同收尾程序 Contract closure procedure 3.最终产品最终产品,服务或成果 Final product,service or result 4.组织过程资产组织过程资产(更新) 2 information 6.可交付成果 Deliverables Organizational process assets(updates) SCOPE范围范围规划范围规划 1.事业环境因素 Enterprise environmental factors 2.组织过程资产组织过程资产 Organizational process assets 3.项目章程 Project charter 4.项目初步范围说明书 Preliminary project scope statement 5.项目管理计划 Project management plan 1.专家判断 Expert judgment 2.样板样板,表格与标准表格与标准Templates,forms,standards 1.项目范围管理计划 Project scope management plan 范围定义范围定义范围定义 1.组织过程资产 Organizational process assets 2.项目章程 Project charter 3.项目初步范围说明书 Preliminary project scope statement 4.项目范围管理计划 Project scope management plan 5.批准的变更申请 Approved change requests 1.产品分析 Product analysis 2.其他方案识别 Alternatives identification 3.专家判断 Expert judgment 4.利害关系者分析 Stakeholder analysis 1.项目范围说明书Project scope statement 2.请求的变更 Requested changes 3.项目范围管理计划 Project scope management plan 制作工作分解结构 Create WBS 1.组织过程资产 Organizational process assets 2.项目范围说明书项目范围说明书 Project scope statement 3.项目范围管理计划 Project scope management plan 4.批准的变更申请 Approved change requests 1.工作分解结构模板 Work breakdown structure templates 2.分解分解 Decomposition 1.项目范围说明书(更新) Project scope statement(updates)_ 2.工作分解结构 Work breakdown structure 3.工作分解结构词汇表 WBS dictionary 4.范围基准 Scope baseline 5.项目范围管理计划(更新) Project scope management plan(updates) 6.请求的变更 Requested changes Scope Verification范围核实1.项目范围说明书Project scope statement 2.工作分解结构词汇表 WBS dictionary 3.项目范围管理计划 Project scope management plan 4.可交付成果 Deliverables 1.检查 Inspection 1.验收的可交付成果 Accepted deliverables 2.请求的变更请求的变更 Requested changes 3. 推荐的纠正措施推荐的纠正措施Recommended corrective actions 范围控制 Scope Control 1.项目范围说明书Project scope statement 2.工作分解结构 Work breakdown structure 3.工作分解结构词汇表 WBS dictionary 4.项目范围管理计划 Project scope management plan 5.绩效报告 Performance reports 6.批准的变更申请 Approved change requests 7.工作绩效信息 Work performance information 1.变更控制系统 Change control system 2.偏差分析偏差分析 Variance analysis 3.补充规划补充规划 Replanning 4.配置管理系统配置管理系统 Configuration management system 1.项目范围说明书(更新) Project scope statement(updates) 2.工作分解结构(更新) Work breakdown structure(updates) 3.工作分解结构词汇表(更新) WBS dictionary(updates) 4.范围基准(更新) Scope baseline(updates) 5.请求的变更 Requested changes 6.推荐的纠正措施推荐的纠正措施Recommended corrective action 7.组织过程资产(更新) Organizational process assets(updates) 8.项目管理计划(更新) Project management plan(updates) TIME进度活动定义 Activity Definition 1.事业环境因素 Enterprise environmental factors 2.组织过程资产 Organizational process assets 3.项目范围说明书 Project scope statement 4.工作分解结构 Work breakdown structure 5.工作分解结构词汇表 WBS clictionary 6.项目管理计划 Progece management plan 1.分解 Decomposition 2.样板 Templates 3.滚动式规划 Rolling wave planning 4.专家判断 Expert judgment 5.规划组成部分 Planning componet 1.活动清单Activity list 2.活动属性 Activity attributes 3.里程碑清单 Milestone list 4.请求的变更 Requested changes 活动排序 Activity Sequencing 1.项目范围说明书项目范围说明书 Project scope statament 2.活动清单活动清单 Activity list 3.活动属性活动属性 Activity attributes 4.里程碑清单里程碑清单 Milestons list 1.紧前关系绘图法(PDM) Precedence Diagramming Method(PDM) 2.箭线绘图法箭线绘图法(ADM) Arrow Diagramming Method(ADM) 1.项目进度网络图 Project schedule network diagrams 2.活动清单活动清单(更新) Activity list (updates) 3 5.批准的变更请求批准的变更请求 Approved change requesta 3.进度网络样板进度网络样板 Schedule network tempiates 4.确定依赖关系确定依赖关系 Dependency determination 5.利用时间提前量与滞后量利用时间提前量与滞后量 Applying leads and lags 3.活动属性活动属性(更新) Activity attributes(updates) 4.请求的变更请求的变更 Requesaed changes 活动资源估算Activity Resource Estimating 1.事业环境因素Enterprise environmental factors 2.组织过程资产 Organizational process assets 3.活动清单Activity list 4.活动属性Activity attributes 5.资源可利用情况 Resouce availability 6.项目管理计划Project management l 1.专家判断 Expert judgment 2.多方案分析 Alternatives analysis 3.出版的估算数据 Published estimating data 4.项目管理软件 Project management sortware 5.自上而下的估算 Bottom estimating 1.活动资源要求 Activity resource requirements 2.活动属性(更新) Activity attributes(updates) 3.资源分解结构 Resource breakdown structure 4.资源日历(更新)Resource calendars 5.请求的变更 Requested changes 活动持续时间估算Activity Duration Estimating 1.事业环境因素Enterprise environmental factors 2.组织过程资产组织过程资产Organizational process assets 3.项目范围说明书项目范围说明书 Project scops statement 4.活动清单活动清单 Activity list 5.活动属性活动属性 Activity attributes 6.活动资源要求活动资源要求 Activity resource requirements 7.资源日历资源日历 Resource calendars 8.项目管理计划项目管理计划 Project management plan ●风险登记册●风险登记册 Risk register ●活动费用估算●活动费用估算 Activity cost estimates 1.专家判断 Expert judgment 2.类比估算 Analogous estimating 3.参数估算 Parametric estimating 4.三点估算 Three-point estimates 5.后备分析 Reserve analysis 1.活动持续时间估算 Activity duration estimates 2.活动属性 Activity attributes(updates) 制定进度表Schedule Development 1.组织过程资产 Organizational process assets 2.项目范围说明书项目范围说明书Project scope statement 3.活动清单活动清单 Activity list 4.活动属性活动属性 Activity attributes 5.项目进度网络图项目进度网络图 Project schedule network diagrams 6.活动资源要求活动资源要求 Activity resource requirements 7.资源日历资源日历 Resource calendars 8.活动持续时间估算活动持续时间估算 Activity duration estimates 9.项目管理计划项目管理计划 Project management plan ●风险登记册 Risk register 1.进度网络分析 Schedule network analysisi 2.关键路线法 Critical path method 3.进度压缩 Schsdule compression 4.假设情景分析What-if scenario analysis 5.资源平衡 Resource leveling 6.关键链法 Critical chain method 7.项目管理软件 Project management software 8.应用日历 Applying calendars 9.调整时间提前滞后量 Adjusting leads and lags 10.进度模型 Schedule model 1.项目进度表项目进度表 Project schedule 2.进度模型数据进度模型数据 Schedule model data 3.进度基准进度基准 Schedule baseline 4.资源要求资源要求 Resource requirements(updates) 5.活动属性活动属性(更新) Activity attributes(updates) 6.项目日历项目日历(更新)Project calendar 7.请求的变更请求的变更 Requesaed changes 8.项目管理计划项目管理计划(更新) Project management plan(updates) ●进度管理计划(更新) Schedule management plan(updates) 进度控制 Schedule Control 1.进度管理计划 schedule management plan 2.进度基准进度基准 Schedule baseline 3.绩效报告绩效报告 Performance reports 4.批准的变更要求批准的变更要求 Approved change requests 1.进度报告进度报告 Progress reporting 2.进度变更控制系统进度变更控制系统 Schedule change control system 3.绩效衡量绩效衡量 Performance measurement 4.项目管理软件项目管理软件 Project management software 5.偏差分析偏差分析 Variance analysisi 6.进度比较横道图进度比较横道图 Schedule comparison bar chars 1. 进度模型数据(更新) Schedule model data(updates) 2. 进度基准(更新) Schedule baseline(updates) 3. 绩效衡量 Performance measurements 4. 请求的变更 Requesaed changes 5.推荐的纠正措施Recommended corrective action 6.组织过程资产(更新) Organizational process assets(updates) 7.活动清单(更新) Activity list(updates) 8.活动属性(更新) Activity attributes(updates) 9.项目管理计划(更新) Project management plan(updates) COST费用费用估算Cost Estimating 1.事业环境因素 Enterprise environmental factors 2.组织过程资产组织过程资产 Organizational process assets 3.项目范围说明书Project scope statement 4. 工作分解结构 Work breakdown structure 1.类比估算 Analogous estimating 2.确定资源费率 Determine resource cost rates 3.自上而下估算 Bottom-up estimating 4.参数估算 Parametric estimating 5.项目管理软件 Project management 1.活动费用估算 Activity cost estimates 2.活动费用估算支持细节活动费用估算支持细节 Activity cost estimate supporting detall 3.请求的变更请求的变更 Requested 4 5 5.工作分解结构词汇表 WBS dictionary 6.项目管理计划 Progece management plan ●进度管理计划●进度管理计划 Schedule management plan ●人员配备管理计划Staffing management plan ●风险登记册 Risk registor software 6.供货商投标分析 Vendor bid analysis 7.准备金分析 Reserve analysis 8.质量成本 Cost of quality changes 4.费用管理计划(更新) Cost management plan(updates) 费用预算 Cost Budgeting 1.项目范围说明书Project scope statement 2.工作分解结构工作分解结构 Work breakdown structure 3.工作分解结构词汇表工作分解结构词汇表 WBS dictionary 4.活动费用估算活动费用估算 Activity cost estimates 5.活动费用估算支持细节活动费用估算支持细节 Activity cost estimate supporting detall 6.项目进度项目进度 Project schedule 7.资源日历资源日历 Resource calendars 8.合同合同 Contract 9.费用管理计划费用管理计划 Cost management plan 1.费用汇总费用汇总 Cost aggregation 2.储备基金分析储备基金分析 Reserve analysis 3.参数估算参数估算 Parametric esrimating 4.资金限制平衡资金限制平衡 Funding limit reconciliation 1.费用基准 Cost baseline 2.项目资金要求 Project funding requirements 3.项目管理计划(更新) Project management plan(updates) 4.请求的变更 Requested changes 费用控制Cost Control 1.费用基准 Cost baseline 2.项目资金要求项目资金要求 Project funding requirements 3.绩效报告绩效报告 Performance reports 4.工作绩效信息 Work performance information 5.批准的变更申请 Approved change requests 6.项目管理计划 Project management plan 1.费用变更控制系统 Cost change control system 2.绩效衡量分析绩效衡量分析 Performance measurements analysis 3.预测预测 Forecasting 4.项目绩效审核项目绩效审核 Project performance reviews 5.项目管理软件 Project management software 6.偏差管理 Variance management 1.费用估算(更新) Cost estimates(update) 2.费用基准(更新) Cost baseline(update) 3.绩效衡量绩效衡量 Performance measurements 4.预测完工预测完工 5.请求的变更请求的变更 Requested changes 6.推荐的纠正措施推荐的纠正措施Recommended corrective action 7.组织过程资产(更新) Organizational process assets(updates) 8.项目管理计划(更新) Project management plan(updates) RISK 风险风险管理规划 Risk Management Planning 1.事业环境因素 Enterprise environmental factors 2.组织过程资产组织过程资产 Organizational process assets 3.项目范围说明书 Project scope statement 4.项目管理计划 Progece management plan 1.规则会议和分析 Planning meeting and analysis 1.风险管理计划 Risk Management Plan 风险识别Risk Identification 1.事业环境因素 Enterprise environmental factors 2.组织过程生产组织过程生产 Organizational process assets 3.项目范围说明书 Project scope statement 4. 风险管理计划 Risk Management Plan 5. 项目管理计划 Project management plan 1.文件审查文件审查 Documentation reviews 2.信息搜索技术信息搜索技术 Information gathering techniques 3.核对表分析核对表分析 Checklist analysis 4.假设分析假设分析 Assumptions analysis 5.图解技术图解技术 Diagiamming techniques 1.风险登记册 Risk register Qualitative Risk Analysisi 风险定性分析风险定性分析1.组织过程生产 Organizational process assets 2.项目范围说明书 Project scope statement 3. 风险管理计划 Risk Management Plan 4. 风险登记册 Risk register 1.风险概率与影响评估 Risk probability and impact assessment 2.概率和影响矩阵概率和影响矩阵 Probablity and impact matrix 3.风险数据质量评估风险数据质量评估 Risk data quality assessment 4.风险分类风险分类 Risk categorization 5.风险紧迫性评估风险紧迫性评估 Risk urgency assessment 1.风险登记册(更新) Risk register(updates) 定量风险分析 Quantitative Risk Analysis 1.组织过程生产 Organizational process assets 2.项目范围说明书 Project scope statement 3. 风险管理计划 Risk Management Plan 4. 风险登记册 Risk register 5. 项目管理计划 Project management plan ●项目进度管理计划 Project schedule management plan ●项目费用管理计划 Project cost management plan 1.数据收集和表示技术 Data gathering and representation techniques 2.定量风险分析和模型技术 Quantitative risk analysis and modeling techniques 1.风险登记册(更新) Risk register(updates) 风险应对规划 Risk Response Planning 1.风险管理计划 Risk Management Plan 2.风险登记册 Risk register 1.消极风险或威胁的应对策略 Strategies for negative risk or threats 2.积极风险或机会的应对策略积极风险或机会的应对策略 Strategies for 1.风险登记册(更新) Risk register(updates) 2.项目管理计划(更新) Project positive risk or opportunities 3.威胁或机会的应对策略威胁或机会的应对策略 Strategies for both threats and opprtunities 4.应急应对策略应急应对策略 Contingent response strategy management plan(updates) 3.与风险有关的合同协议与风险有关的合同协议 Risk-related contractual agreements 风险监控 Risk Monitoring and Control 1.风险管理计划 Risk Management Plan 2.风险登记册 Risk register 3.批准的变更申请 Approved change requests 4.工作绩效信息 Work performance information 5.绩效报告 Performance reports 1.风险再评估 Risk reassessment 2.风险审计风险审计 Risk audits 3.变差和趋势分析变差和趋势分析 Variance and trend analysis 4.技术绩效分析技术绩效分析 Technical performance measurement 5.储备金分析储备金分析Reserve analysis 6.状态审查会状态审查会 Status meetings 1.风险登记册(更新) Risk register(updates) 2.请求的变更 Requested changes 3.推荐的纠正措施推荐的纠正措施Recommended corrective action 4.推荐的预防措施推荐的预防措施Recommended preventive action 5.组织过程资产(更新) Organizational process assets(updates) 6.项目管理计划(更新) Project management plan(updates) QUALITY质量质量规划 Quality Planning 1.事业环境因素 Enterprise environmental factors 2.组织过程资产 Organizational process assets 3.项目范围说明书Project scope statement 4.项目管理计划 Progece management plan 1.成本效益分析成本效益分析 Cost-benefit analysis 2.基准对照基准对照 Benchmarking 3.试验设计试验设计 Design of experiments 5.质量成本质量成本(COQ) Cost of quality (COQ) 6.其他质量规划工具其他质量规划工具 Additional quality planning tools 1.质量管理计划质量管理计划 Quality management plan 2.质量测量指标质量测量指标 Quality metrics 3.质量核对表质量核对表 Quality checklists 4.过程改进计划过程改进计划 Process improvement plan 5.质量基准质量基准 Quality baseline 6.项目管理计划项目管理计划(更新) Project management plan(updates) 实施质量保证Perform Quality Assurance 1.质量管理计划质量管理计划 Quality management plan 2.质量测量指标质量测量指标 Quality metrics 3.过程改进计划过程改进计划 Process improvement plan 4.工作绩效信息 Work performance information 5.批准的变更申请 Approved change requests 6.质量控制衡量 Quality control measurnments 7.实施的变更请求 Implementde change requests 8.实施的纠正措施 Implementde corrective actions 9.实施的缺陷补救 Implementde defect repair 10.实施的预防措施 Implementde preventive actions 1.质量规划工具与技术质量规划工具与技术 Quality planning tools and techniques 2.质量审计质量审计 Quality audits 3.过程分析过程分析 Process analysis 4.质量控制工具与技术质量控制工具与技术 Quality control tools and techniques 1.请求的变更请求的变更 Requested changes 2.推荐的纠正措施推荐的纠正措施推荐的纠正措施Recommended corrective action 3.组织过程资产(更新) Organizational process assets(updates) 4.项目管理计划(更新) Project management plan(updates) 实施质量监控 Perform Quality Control 1.质量管理计划质量管理计划 Quality management plan 2.质量测量指标质量测量指标 Quality metrics 3.质量核对表质量核对表 Quality checklists 4.组织过程资产组织过程资产 Organizational process assets 5.工作绩效信息工作绩效信息 Work performance information 6.批准的变更请求批准的变更请求 Approved change requests 7.可交付成果可交付成果 Deliverables 1.因果图因果图 Cause and effect diagram 2.控制图控制图 Control charts 3.流程图流程图 Flowcharting 4.直方图直方图 Histogram 5.帕雷托图帕雷托图 Pareto chart 6.趋势图趋势图 Run chart 7.散点图散点图 Scatter diagram 8,统计抽样统计抽样 Statistical sampling 9.检查检查 Inspection 10.缺陷补救审查缺陷补救审查 Defect repair review 1.质量控制衡量质量控制衡量 Quality control measurnments 2.确认的缺陷补救确认的缺陷补救 Validated defect repair 3.质量基准质量基准(更新) Quality baseline(updates) 4.推荐的纠正措施推荐的纠正措施推荐的纠正措施Recommended corrective action 5.推荐的预防措施推荐的预防措施推荐的预防措施Recommended preventive action 6.请求的变更 Requested changes 7.推荐的缺陷补救推荐的缺陷补救Recommended defect repair 8.组织过程资产 Organizational process assets 9.确认的可交付成果 Validated deliverables 10.项目管理计划(更新) Project management plan(updates) HUMAN RESOURCE人力资源人力资源规划人力资源规划 1.事业环境因素 Enterprise environmental factors 2.组织过程资产 Organizational process assets 1.组织机构图和岗位描述组织机构图和岗位描述 Organization charts and position descriptions 2.交际交际 Networking 3.组织理论组织理论 Organization theory 1.角色与职责角色与职责 roles and responsibilities 2.项目组织图项目组织图 Projece organization chares 6 7 3.项目管理计划 Progece management plan ●活动资源需求 Activity resource requirements 3.人员配备管理计划人员配备管理计划 Staffinf management plan 项目团队组建 Acquire Project Team 1.事业环境因素 Enterprise environmental factors 2.组织过程资产 Organizational process assets 3.角色与职责 roles and responsibilities 4.项目组织图 Projece organization chares 5.人员配备管理计划 Staffinf management plan 招聘惯例招聘惯例 1.预分派预分派 Pre-assignment 2.谈判谈判 Negotiation 3.招募招募 Acquisition 4.虚拟团队虚拟团队Virtual teams 1.项目人员分派到位项目人员分派到位 Project staff assignments 2.资源可利用情况资源可利用情况 Resource availability 3.人员配备管理计划人员配备管理计划(更新) Staffinf management plan(updates) 项目团队建设 Develop Project Team 1.项目人员分派 Project staff assignments 2.人员配备管理计划人员配备管理计划 Staffinf management plan 3.资源可利用情况 Resource availability 1.通用管理技能通用管理技能 General management skills 2.培训培训 Training 3.团队建设活动团队建设活动 Team-building activities 4.规则规则 Ground rules 5.集中办公集中办公 Co-location 6.奖励与表彰奖励与表彰 Recognition and rewards 1.团队绩效评估 Team performance assessment 项目团队管理 Manage Project Team 1.组织过程资产组织过程资产 Organizational process assets 2.项目人员分派项目人员分派 Project staff assignments 3.角色与职责角色与职责 roles and responsibilities 4.项目组织图项目组织图 Projece organization chares 5.人员配备管理计划 Staffinf management plan 6.团队绩效考核 Team performance assessment 7.工作绩效信息 Work performance information 8.绩效报告 Performance reports 1.观察与交谈观察与交谈 Observation and conversation 2.项目绩效评估项目绩效评估 Project performance appraisals 3.冲突管理冲突管理 Conflict management 4.问题登记薄问题登记薄 Lssue log 1.请求的变更 Requested changes 2.推荐的纠正措施推荐的纠正措施Recommended corrective action 3.推荐的预防措施推荐的预防措施Recommended preventive action 4.组织过程资产(更新) Organizational process assets(updates) 5.项目管理计划(更新) Project management plan(updates) COMMUNICATIONS 沟通Communications Planning 沟通规划沟通规划1.事业环境因素 Enterprise environmental factors 2.组织过程生产组织过程生产 Organizational process assets 3.项目范围说明书Project scope statement 4.项目管理计划 Progece management plan ● 制约因素 Constraints ● 假设 Assumptions 1.沟通需求分析沟通需求分析 Communications requirements analysls 2.沟通技术沟通技术 Communications technology 1.沟通管理计划 Communications management plan Information Distribution 信息发布发布1. 沟通管理计划 Communications management plan 1.沟通技能 Communications skills 2.信息收集和检索系统 Information gathering and retrieval system 3.信息发布系统 Information distribution methods 4.经验教训总结过程 Lessons learned process 1. 组织过程生产(更新) Organizational process assets(updates) 2. 请求的变更请求的变更 Requested changes Performance Reporting 绩效报告报告1.工作绩效信息 Work performance information 2.绩效衡量 Performance measurements 3.完工预测 Forecasted completion 4.质量控制衡量 Quality control measurnments 5.项目管理计划 Project management plan ●绩效衡量分析 Performance measurements baseline 6.批准的变更申请 Approved change requests 7.可交付成果 Deliverables 1.信息演示工具 Information presentation tools 2.绩效信息收集和汇总 Performance information gathering and compilation 3.状态审查会 Status review meetings 4.工时汇报系统Time reporting systems 5.费用汇报系统Cost reporting systems 1.绩效报告 Performance reports 2.预测 Forecasts 3.请求的变更 Requested changes 4.推荐的纠正措施推荐的纠正措施Recommended corrective action 5.组织过程资产(更新) Organizational process assets(updates) 利害关系者管理 Manage Stakeholders 1.沟通管理计划 Communications management plan 2. 组织过程资产 Organizational process assets 1.沟通方法 Communications methods 2.问题登记薄 lssue logs 1.问题得以解决Resolved issues 2.批准的变更申请 Approved change requests 3.批准的纠正措施 Approved corrective action 4.组织过程资产(更新) Organizational process assets(updates) 5.项目管理计划(更新) Project management plan(updates) PROCUREMENT采购采购规划 Plan Purchases and Acquisitions 1.事业环境因素 Enterprise environmental factors 2.组织过程生产组织过程生产 Organizational process assets 3.项目范围说明书Project scope statement 4.工作分解结构 Work breakdown structure 5.工作分解结构词汇表 WBS clictionary 6.项目管理计划 Progece management plan ●风险登记册 Risk register ●与风险有关的合同协议 Risk-related contractual agreements ●资源要求 Resource requirements ●项目进度计划 Project schedule ●活动费用估算 Activity cost estimate ●费用基准 Cost baseline 1.自制或外购分析自制或外购分析 Make-or-buy analysls 2.专家判断专家判断 Expert judgment 3.合同类型合同类型 Contract types 1.采购管理计划 Procurement management plan 2.合同工作说明书 Contract statement of work 3.自制或外购决策 Maker-or-buy changes 4.请求的变更 Requested changes 发包规划 Plan Contracting 1.采购管理计划 Procurement management plan 2.合同工作说明书 Contract statement of work 3.自制或外购决策自制或外购决策 Maker-or-buy changes 4.项目管理计划 Project management plan ●风险登记册 Risk register ●与风险有关的合同协议●与风险有关的合同协议 Risk-related contractual agreements ●资源要求●资源要求 Resource requirements ●项目进度计划 Project schedule ●活动费用估算 Activity cost estimate ●费用基准 Cost baseline 1.标准表格标准表格 Standard forms 2.专家判断专家判断 Expert Judgment 1.采购文件 Procurement documents 2.评估标准 Evaluation criteria 3.合同工作说明书(更新) Contract statement of work(updates) 询价Request Seller Responses 1.组织过程资产 Organizational process assets 2.采购管理计划 Procurement management plan 3.采购文件 Procurement documents 1.招标人会议招标人会议 Bldder conferences 2.刊登广告刊登广告 Advertising 3.制定合格卖方清单制定合格卖方清单 Develop qualifid sellers list 1.合格卖方清单 Qualified sellers list 2.采购文件包采购文件包 Procurement document package 3.建议书建议书 Proposals 卖方选择Select Sellers 1.组织过程资产 Organizational process assets 2.采购管理计划 Procurement management plan 3.评估标准 Evaluation criteria 4.采购文件包 Procurement document package 5.建议书 Proposals 6.合格卖方清单 Qualified sellers list 7.项目管理计划 Project management plan ●风险登记册 Risk register ●与风险有关的合同协议●与风险有关的合同协议 Risk-related contractual agreements 1.加权系统加权系统 Weighting system 2.独立估算独立估算 Independent estimates 3.筛选系统筛选系统 Screening system 4.合同谈判合同谈判 negotiation 5.卖方评级系统卖方评级系统 Seller rating systens 6.专家判断专家判断 Expert judgment 7.建议书评估技术建议书评估技术 Proposal evaluation techniques 1.选中的卖方 Selected sellers 2.合同合同 Contract 3.合同管理计划合同管理计划 Contract management plan 4.资源可利用情况资源可利用情况 Resource availability 5.采购管理计划采购管理计划(更新) Procurement management plan(updates) 6.请求的变更请求的变更 Requested changes 合同管理 Contract Administration 1.合同合同 Contract 2.合同管理计划合同管理计划 Contract management plan 3.选中的卖方选中的卖方 Selected sellers 4.绩效报告 Performance reports 5.批准的变更申请 Approved change requests 6.工作绩效信息 Work performance information 1.合同变更控制系统 Contract change control system 2.买方进行的绩效审核买方进行的绩效审核 Buyer-conducted per-formance review 3.检验和审计检验和审计 Inspections and audits 4.绩效报告绩效报告 Performance reporting 5.支付系统支付系统 Payment system 6.索赔管理索赔管理 Claims administration 7.合同档案管理系统合同档案管理系统 Records management system 8.信息技术 Information technology 1.合同文件合同文件 Contract documentation 2.请求的变更请求的变更 Requested changes 3.推荐的纠正措施推荐的纠正措施推荐的纠正措施Recommended corrective action 4.组织过程资产(更新) Organizational process assets(updates) 5.项目管理计划(更新) Project management plan(updates) ●采购管理计划 Procurement management plan ●合同管理计划 Contract management plan 合同收尾 Contract Closure 1.采购管理计划 Procurement management plan 2.合同管理计划 Contract management plan 3.合同文件 Contract documentation 4.合同收尾程序 Contract closure procedure 1.采购审计采购审计 Procurement audits 2.合同档案管理系统合同档案管理系统 Records management system 1.合同收尾Contract closures 2.组织过程资产组织过程资产(更新) Organizational process assets(updates) 8 。

项目管理计划模板(英文DOC 16页)

<Project Name>Project Management PlanVersion <x.x> [Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.]Distribution List[State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]Table of Contents1.Introduction 51.1Purpose 51.2Scope 51.3Definitions, Acronyms and Abbreviations 51.4References 51.5Overview 52.Project Overview 62.1Project Name, Code and Leader 62.2Project Purpose, Scope and Objectives 62.3Assumptions and Constraints 62.3.1Critical Assumptions and Constraints 62.3.2Non-Critical Assumptions and Constraints 62.4Project Milestones 62.5Project Deliverables 62.6Tailoring Guidelines 72.7Software Development Life Cycle 73.Project Organization 83.1Organizational Structure 83.2External Interfaces 103.3Roles and Responsibilities 103.3.1<Organizational Unit Name> 104.Management Process 114.1Work Breakdown Structure (WBS) 114.2Project Estimates 114.2.1Estimation Technique 114.2.2Size 114.2.3Effort 114.3Project Schedule 114.3.1Pre-Development Schedule 114.3.2Development Schedule 114.4Project Phases, Iterations and Releases 114.4.1Project Phases 114.4.2Project Iterations 114.4.3Releases 114.5Project Resourcing 114.5.1Staffing 114.5.2Resource Acquisition 124.5.3Training 124.6Project Budget 124.7Project Monitoring and Control 124.7.1Schedule Control 124.7.2Budget Control 124.7.3Measurements 124.8Risk Management Plan 124.9Project Closure 125.Technical Process Plans 135.1User Experience Design 135.2Requirements Management 135.3Analysis and Design 135.4Development Plan 135.5Peer Review Plan 135.6Project Maintenance 135.7Test Plan 135.8Tools, Techniques and Standards 135.8.1Tools 135.8.2Techniques and Standards 145.9Infrastructure 145.10Facilities 145.11Security Plan 156.Supporting Process Plans 156.1Configuration Management Plan 156.2Documentation 156.3Software Quality Assurance Plan 156.4Intergroup Coordination 156.5Communication 156.6Problem Resolution 156.7Subcontractor Management 157.Additional plans 168.Appendices 16Project Management Plan1. Introduction[The introduction of the Project Management Plan should provide an overview of the entiredocument. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]1.1 Purpose[Specify the purpose of this Project Management Plan.]1.2 Scope[A brief description of the scope of this Project Management Plan; what Project(s) it isassociated with, and anything else that is affected or influenced by this document.]1.3 Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms, acronyms, and abbreviationsrequired to interpret properly the Project Management Plan. This information may be provided by reference to the project Glossary.]1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in theProject Management Plan. Each document should be identified by title, report number (ifapplicable), date, and publishing organization. Specify the sources from which the referencescan be obtained. This information may be provided by reference to an appendix or to anotherdocument. For the Project Management Plan, the list of referenced artifacts may include:•Risk Management Plan•User Interfaces Guidelines•Configuration Management Plan•Software Quality Assurance Plan, etc.]1.5 Overview[This subsection should describe what the rest of the Project Management Plan contains andexplain how the document is organized.]2. Project Overview2.1 Project Name, Code and Leader[Specify the project name, project code and project leader (project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2 Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expected to deliver.]2.3 Assumptions and Constraints[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project. Make a distinction between critical and non-criticalfactors.]2.3.1 Critical Assumptions and Constraints[State the critical assumptions and constraints affecting the project.]2.3.2 Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4 Project Milestones[Tabular list of major milestones to be achieved during the project, with target dates.]2.5 Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]2.6 Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7 Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]3. Project Organization3.1 Organizational Structure[Describe the organizational structure of the project team, including management and otherreview authorities. This should include identification of all project organizational units and adescription of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:•Project Implementation Committee•Project Steering Committee•Project Management Team•Architecture Group•User Experience Design Team•Requirements Team•Analysis and Design Team•Implementation Group•Development Team•Database Management Team•Testing Team•Infrastructure Team•Configuration Management Team•Software Quality Assurance Team, etc.]3.2 External Interfaces[Describe how the project interfaces with external groups. For each external group, identify the internal/external contact names.]3.3 Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.] 3.3.1 <Organizational Unit Name>4. Management Process4.1 Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2 Project Estimates4.2.1 Estimation Technique[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as the basis for those estimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2 Size[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]4.2.3 Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation.Units may be man-hours, man-days, etc.]4.3 Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points,demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]4.3.1 Pre-Development Schedule[This schedule will cater for project planning, requirements, analysis and design activities.]4.3.2 Development Schedule[This schedule will cater coding, testing and deployment activities.]4.4 Project Phases, Iterations and Releases4.4.1 Project Phases[Identify phases and major milestones with their achievement criteria.]4.4.2 Project Iterations[Specify the number of iterations and list the objectives to be accomplished for each of theiterations.]4.4.3 Releases[Brief descriptions of each software release, whether demo, beta, etc.]4.5 Project Resourcing4.5.1 Staffing[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]4.5.2 Resource Acquisition[Describe how you will approach finding and acquiring the staff needed for the project.]4.5.3 Training[List any special training project team members will require, with target dates for when thistraining should be completed.]4.6 Project Budget[Allocation of costs against the WBS and the project phases.]4.7 Project Monitoring and Control4.7.1 Schedule Control[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]4.7.2 Budget Control[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]4.7.3 Measurements[Describe the types of measurements to be taken, their frequency, and responsibleworkers/entities for this purpose.]4.8 Risk Management Plan[Enclosed by reference]4.9 Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]5. Technical Process Plans5.1 User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.2 Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.3 Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.4 Development Plan[Enclosed by reference]5.5 Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6 Maintenance[Describe details of any software maintenance for the warranty period of the project.]5.7 Test Plan[Enclosed by reference]5.8 Tools, Techniques and Standards5.8.1 Tools5.8.1.1 Project Management Tools[Specify the project management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, projectmonitoring, status reporting, measurements, etc. Examples of these tools are MS Project, etc.]5.8.1.2 Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issueresolution, requirement change management, measurements, etc. Examples of these tools areRational Requisite Pro, EINS, etc.]5.8.1.3 System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasonsfor their selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]5.8.1.4 Languages[Specify the languages that are to be used for software development in the project and thereasons for their selection. Examples of languages are HTML, Java, etc.]5.8.1.5 User-Interface Development Tools[Specify the tools that are to be used for UI development in the project and the reasons for their selection. Examples of these tools can be Dreamweaver, Flash, etc.]5.8.1.6 Database Management System Software[Specify the database management system software that is to be used in the project and thereasons for their selection. Examples of these tools are Oracle, SQL Server, etc.]5.8.1.7 Third Party Software[Specify any third party software that is to be used in the project and the reasons for theirselection. Examples are Inktomi, Infranet, etc.]5.8.1.8 Software Testing Tools[Specify the software testing tools that are to be used in the project and the reasons for theirselection. Examples of these tools are WinRunner, LoadRunner, etc.]5.8.1.9 Defect and Change Management Tools[Specify the defect and change management tools that are to be used in the project and thereasons for their selection. Examples of these tools are ClearQuest, etc.]5.8.1.10 Configuration Management Tools[Specify the configuration management tools that are to be used in the project and the reasonsfor their selection. Examples of these tools are ClearCase, etc.]5.8.1.11 Integrated Development Environment[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.]5.8.2 Techniques and Standards[Lists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]5.9 Infrastructure[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]5.10 Facilities[Describe the facilities required for the execution of the project. This will cover physicalworkspace, buildings, etc.]5.11 Security Plan[List down the security consideration e.g. of security can be operating system, access controls to site/product, physical security considerations.]6. Supporting Process Plans6.1 Configuration Management Plan[Enclosed by reference]6.2 Documentation[Specify the documents that will be produced in the project, what document templates will beused, and any other information pertaining to documentation.]6.3 Software Quality Assurance Plan[Enclosed by reference]6.4 Intergroup Coordination[Describe how different project groups will communicate with one another; specify dependencies, and commitments.]6.5 Communication[Specify how various workers/units/entities, both within and outside the project team, willcommunicate with each other.]6.6 Problem Resolution[Describe the approach for resolving issues in the project, escalation procedures, etc.]6.7 Subcontractor Management[If subcontractors are involved in the project give details of what kind of contractors are required for various tasks, the duration for which they are required and how they will be managed.]7. Additional plans[Additional plans if required by contract or regulations.] 8. Appendices[Attach any supplementary information.]。

project management项目管理计划书,英文版

G M303P R O J E C T M A N A G E M E N TName: Sixiao WuID: 5053500160BBA & Batch: 7-2As a result of project management's superiority and the characteristic, it may apply nearly in any single case. Launches a satellite, the Olympic Games, the presidential election, a wedding ceremony, even is the supper. This concept looks like very complicate but really useful. Here is an easy way to make it so shallow and clear that it is easy to understand. Everybody knows pretty much about dinner, because we eat every night. The process of dinner preparing is typical projects which are unique, disposable and irreversible. Let’s see how PM theory is in an ordinaries matter to give full play in the daily life.Well begun is half done。

Only achieves the project goal called successful. But the goal was determined when we starting. Specifically speaking, this process needs to analyze the relate person, the determination project goal as well as discovers the restriction factor and the supposition.Analyzes the relate person's demand and affects the project successful standard objectively achieves the project goal, subjectively is the relate person is satisfied. Satisfaction premise is understood that relate person demand, what needs to pay attention, one is the relate person is not explicit expresses the latent demand, project manager needs to have the outstanding communication ability to understand that its potential demand, another spot is the project relate person the demand is often inconsistent, will be sometimes contradictory, we must record their respective demand, and will try to let it balanced.After understanding demand issues, needs to transform the demand as the concrete goal. The goal and the demand are different, the demand is one kind of feeling, but the goal must be conforms to the SMART principle (concretely, to be possible to weigh, May to realize related, has time limit). The project goal may describe from four aspects: The scope (what to do what not to do), progress (which means to do the m atter, when and what will do, and how much time will takes to do), the cost (spends how much money), the quality (achieves up to goal requisition).Now we will use those theories to deal with real case, first of all we should:Establishing objectivesThe definite supper project's goal is as follows:1) Scope goal: The achievement must include 4 main dish, 1 soup and thestaple food (rice or anything else), in matching needs to have food and soup, hot and cold dish.2) The progress goal: The project must complete in 2 hours, the starttime is 4:00 pm, and completes the time for 6:00 pm3) The quality objectives: yummy and health.4) Cost goal: The direct cost is raw material cost; the indirect costs arethe water, the electricity and so on.Priority targetusually the relate person will set many goals, some goals will sometimes be contradictory, for instance the wish scope must wide, the progress probably quick, the cost probably few, the quality be as well as possible. At this moment, we must determine which one should coming first. The advantage is: May concentrate the energy to satisfy the critical target.WBS Work break-dow n scheduleFormulates WBS is the relapse process, needs to discuss repeatedly. Below is my supper project WBS (graph 1).The most underlying bed is the work package, is the noun (cooks spareribs in here is dish name). Under initial WBS the main food has included the rice, the Dumpling, Deep-fried dough cake; Because the wheaten food works complex, considered the time limit is improper, if goes out to purchase needs to spend the extra cost, therefore we cut ii off, determined finally the main food work package is the rice.Organization:Now we clear project's scope and the step, then, needed to det ermine the project essential activity. Saving of time's best method only does the essential matter, what is called the essential matter? It cans influential the final result direct. Many people in the routine work, are accustomed to the motion, is not accustomed to the ponder matter's necessity, causes the wasted effort. How to determine that which move are necessary. May decomposed each work package, must ponder to obtain this work package, and needs to engage in any concrete activity. At this moment, may use the active detailed list (to see graph 2) to organized activities.Determining the project scheduleAfter determining which the essential activities are, analysis it logistically, be sure the order. The method is simple, to each activity, before starting it which process has to complete? And end of this part what we have to deal with? After analyzing the order, for direct-viewing expression activity logical relation we should draw up the network chart clearly (to see graph 3). Through the network chart, may let a staff clear their duty, reduces the manager spend the time in coordinated aspect. After completing the network chart, might find the longest way, this way was the critical path. In critical path's activity needs to pay attention highly, because of the key activity's delay, will cause the project progress to have the problem.Gantt chartWinds the chart to be able to express the logical relation.We are wondering let the management has direct-viewing, understand the project progress clearly. We use the Gantt chart to express the final progress chart. The Gantt chart usually (sees graph4) Left side to list the active name, the upper right tell time rod, right expresses each active lasting with the by-way.In this case, we put this project into 3 different PM theory model to explore how it works.I Cycle theoryAccording to cycle theory, “the supper project”may divide into it such several project stages:1). Initiating a project: decide have dinner tonight at home, makes theapproximate time to arrange2). Demand investigation: Asks that the family members what they want3). Demand analysis: consider about all related Factors overall evaluationseason, weather, control body weight, definite cuisine4). System design: Designs each vegetable the main dish and condiment5). Development: Goes out to purchase, then starts to prepare food6). System test: Tastes7). Deployed: Sets the table eats meal8). Project conclusion: Tidies up dishes and bowlsII CMMI1). PP(project planning): Does the plan supper's cookbook, which rawmaterials need to purchase, makes the approximate time to arrange2). PMC (project track and monitoring): Inspect every time after completea step, if overtime has made essential adjustment3). RM(requirements management): Carries on the management to thefamily member to the cuisine request, guaranteed that each request is managed, or is satisfied, or is cancelled, or is changed4). CM(disposition management): To supper preparation process's eachfinished product, the half-finished product and other sideline products carry on the management;5). MA (measure and analysis): make forecasting, to measure and analysisevery detail of raw material, operating time and so on.6). PPQA(process and product quality guarantee) - - carry on theappraisal regularly to the supper preparation process, make sure each single process in our plan, and the result pass muster;7). SAM(supplier management) If we outsourcing part of job in thepreparation process. Such as on-line order partial raw materials or something else, we need to monitor and charge it and finally let everything going well.III PMPAccording to the PMP project management system, “the supper project”will be divided into the following of knowledge:1). Scope management: Definite cookbook2). Quality control:Guarantees raw material to be fresh, the vegetableflavor conforms to the family member to request3). Procurement management: If on-line ordered the red wine or other rawmaterials, we need to charge on the due time and goods by delivers 4). Time management:In the entire supper project process, guaranteedthat completes according to the plan progress5). Human resources management:If have several helper to work with,must charge on everyone’s task and division6). Risk management: The attention distinguishes and monitors each kindof contingency which in the whole process possibly appears, and draws up contingency plan7). Cost management:Guaranteed that this supper do not exceedexpenditures8). Communication management: In the supper preparation's process, mustto each person (for instance family member) the prompt notification progress, if the somebody's demand changes, must communicate promptly9). Whole management: As the supper preparation's person in charge, must carry on to above each aspect work supervises and controlsConclusionNow we know about the project management knowledge, when actually implements the project, many people easy to neglected one thing. Decision-making is rash, plan is not thorough, execution is not firm, controlling is ineffectual, so is definitely impossible to have a happy ending. Induces, I find this model which such simple may operate:A goal: As the project, its major goal must be correct, clear and feasible.Three management:Resource management, communication m anagement, risk management。

软件项目之配置管理计划(范文1)

XXXX项目配置管理计划简介本计划描述了配置组织结构以及贯穿项目组日常工作，由项目组识别并定义的一系列的配置项的实践过程。

1.1文档目的定义配置管理的职责、所需资源以及描述实施过程中一系列的配置管理活动，指导项目软件配置管理工作。

1.2适用范围本计划适用于XXXX项目的软件配置管理活动的制定。

1.3项目背景描述略。

1.4术语与缩略语软件配置管理：简称 SCM（Software Configuration Management），是在项目开发中，标识、控制和管理软件变更的一种管理。

配置项目标识：（Configuration Indentification）对软件项目在开发过程中的资源进行标识，以便标识。

配置审计：（Configuration Audit）对软件配置管理过程中的行动进行检查。

资源2.1配置管理组织架构图配置管理的组织架构主要角色有公司的配置管理（Configuration Management，CM），项目的配置管理（Configuration Management，CM），项目经理（Project manager，PM），以及配置管理审批人和项目成员。

图1 组织架构图2.2关键角色和职责配置管理员项目组中负责配置管理工作的角色，负责计划和控制配置管理过程。

在某一开发阶段通过评审或某一质量检查点通过审核后，配置管理员负责统计添加或修改相关产出物的最新有效版本以及审核证明。

配置管理委员会（CCB）CCB 是一个虚拟的小组，对配置管理各项活动拥有决策权（例如审批配置管理计划，审批配置项变更请求等）。

CCB 的决策采用“少数服从多数”的原则。

主要成员：甲方项目经理、高层领导、需求专家、架构专家、配置管理人员、测试专家和质量保证人员。

2.3所需资源表1 配置管理工具及辅助软件工具名称发布公司用途GitLab GitLab 配置库管理工具，主要源代码SVN Apache软件基金会配置库管理工具，主要是文档Microsoft Office Microsoft 办公工具Microsoft Project Microsoft 办公工具SCM 活动3.1配置库的创建和授权项目配置库创建项目配置库申请审批通过后，项目经理通过一体化运维平台的工作单给项目组配置管理员，要求开通配置库，并说明项目人员权限。

ITSM项目SOW(工作范围)说明书模版

如果没有特殊指明，客户收到BB公司的提交物后，对交付物进行审核或提出修改意见，在3个工作日内作出批复接受或拒绝交付物，超过3个工作日没有批复，为默认接受。
除非特殊说明，本工作内容说明中描述的服务均不包括未来（项目结束后）对产品的升级和支持。
BB工程实施一般在正常的工作时间，即星期一至星期五的8:30AM到5:00PM，节假日除外。
AAAA配置管理流程培训
熟悉配置管理流程设计
1天
AAAA指定项目相关人员
AAAA变更管理流程培训
熟悉变更管理流程设计
1天
AAAA指定项目相关人员
AAAA发布管理流程培训
熟悉发布管理流程设计
1天
AAAA指定项目相关人员
AAAA财务管理流程培训
熟悉财务管理流程设计
1天
AAAA指定项目相关人员
BB针对AAAA的指定人员提供由BB培训部举办的不超过2次的ITIL Foundation的专班培训。
3.4.1.3.
按项目计划要求配合BB咨询顾问进行必要的访谈和交流会议；配合BB完成针对AAAA特定环境的流程执行活动的具体技术细节或步骤的编写。
3.4.2.
3.4.2.1.
基于ITIL参考模型及BBITSM方法论针完成AAAA问题管理的流程咨询设计，包括以下内容：
ITIL基础理念及问题管理的流程宣导
与其他ITIL流程进行有机集成
确定合适的配置项管理深度和级别，帮助数据中心建立配置项的合理分类
设立配置项的状态、属性、命名规则及其之间的关系
制定合理的人员角色和职责及考核机制
设立合理的流程衡量指标KPI
配置管理流程未来改进建议
流程管理规章制度，包括配置流程管理保障的原则，分工和责任，操作指导性建议

华为项目管理10大模板(格式调整,可直接使用)课件【新版】

六、项目主要利益干系人（包括高管、客户、职能部门主管、供应商、项目赞助人、项目经理、项目组成员等干系人）
成员姓名项目角色
所在部门
职责
Name 李四
Project Role 项目赞助人
A 国代表处
Reponsibility 项目赞助
Sponsor
张三
项目经理
VIP 客户
总体负责
Manager
接
王五
项目核心成员
待A 策国划代处表处客户关系
Core team
赵六
项目核心成员
GTS 重大项
extended team
际行销部
持
XXX
项目非核心成员 GTS 重大项技术服务支
extended team
目部
持
XXX
项目非核心成员供应链管理供应链支持
extended team
部
XXX
项目其他人员
A 国代表处客户关系
Other personel
XXX
பைடு நூலகம்
项目其他人员
客户工程部客户接待
Other personel
project milestones)
7月8日
7 月 11 日
成立项目组
递交邀请函
7 月 14 日行程确认
7 月 17 日启程
7 月 22 日考察结束
7 月 25 日回访
四、评价标准（说明项目成果在何种情况下将被接受）IV. Project acceptance criteria (to describe conditions under
Core team
目部
吴丹

全套CMMI(信息系统项目管理)文档模板-项目计划书(项目策划)

项目计划书目录1概述 (1)1.1目的 (1)1.2范围 (1)1.3术语和缩写 (2)2项目信息 (2)2.1项目背景 (2)2.2项目范围 (2)2.3项目约束 (3)3软件生命周期 (3)4项目进度安排 (6)5项目监督 (7)6人力资源计划 (8)8数据资料管理计划 (13)9软硬件资源和管理工具计划 (15)10关键依赖 (16)11沟通计划 (17)12干系人介入计划 (20)13风险管理计划 (26)14软件工程计划 (27)14.1需求管理计划 (27)14.1.1需求管理的工作产品列表 (27)14.1.2需求状态的跟踪及追溯 (28)14.2需求变更管理 (28)14.3设计计划 (29)14.4实现 (29)14.5测试计划 (29)15项目从属计划 (29)15.1度量计划 (29)15.2配置管理计划 (29)15.3质量保证计划 (29)15.4.1评审环境配置 (31)15.4.2评审的标准 (31)1概述1.1目的明确项目开发的全过程，规定了在开发过程中需要完成的活动和目标，为本项目的实施提供指导依据。

本文档的读者包括项目经理、系统分析人员、开发人员、测试人员、QA以及相关部门的接口人员等。

1.2范围本项目计划适用于《丰县云计算数据资源管理平台》项目。

本文涉及内容包括：项目计划完成的活动及其目标；项目采用的质量计划；项目的交付件；项目采用的质量计划；项目进度；项目的配置管理；项目的风险管理。

1.3术语和缩写2项目信息2.1项目背景随着网络技术的逐步成熟，网络服务的不断增加，互联网行业已经进入了一个高速发展期。

传统的需求设计，开发测试，上线部署的软件开发模式已经很难满足这些企业快速的发展需求。

而于此同时另一种新的按需付费的软硬件交付模式越来越受到许多企业青睐。

本项目旨在为相关管理工作提供一个科学、便捷的软件平台，提高管理水平，提高工作效率。

2.2项目范围该系统将实现丰县云计算数据资源中心的产品服务宣传和管理。

计划书作文的模板英语

计划书作文的模板英语英文回答：Project Plan Template。

1. Executive Summary。

A brief overview of the project, including its purpose, goals, and objectives.2. Project Scope。

A detailed description of the project's deliverables, timeline, and budget.3. Project Team。

A list of the project team members, their roles, and responsibilities.4. Project Plan。

A detailed plan for completing the project, including milestones, deadlines, and resources.5. Risk Management。

A plan for identifying, assessing, and mitigatingrisks that could impact the project.6. Quality Assurance。

A plan for ensuring that the project deliverables meet the required quality standards.7. Communication Plan。

A plan for communicating with stakeholders throughout the project.8. Monitoring and Evaluation。

A plan for tracking project progress and evaluating its success.中文回答：计划书模板。

项目策划管理计划模板(英文)

IFS 项目管理方案

01.01.01 SYX management team
ShipyardXchange has appointed the complete management team. Harald Rafdal is appointed CEO ....
New suppliers Brunvoll AS ABB Installasjon AS Rolls-Royce Marine AS Davit International GmbH Pay & Brinck Motor AS KGW Scheriner Maschinenbau WärtsiläNorway AS
投资建立莱福士造船项目，主要是相中蓬莱西城临港工业区的良好港口优势，该项目主要设计生产难度比较大、技术要求严的豪华游艇及万吨巨轮，生产销售各种压力容器、海上石油工程设施、大型钢结构和混凝土结构产品及船舶配套设备、舾装件，并为20万吨巨轮配套生产大件。项目投产后，年生产各类船只100余艘，生产配件可达 3．2万(套)件，实现销售收入40多亿元，并将逐步成为胶东船舶制造业中心。该项目分三期工程进行，第一期计划投入2亿元人民币，新建600米舾装码头和200米X 45米X10米干船坞一座，并配套建造万吨级以上船舶所需的生产设施、设备。第二期新建200米X60米 X10米干船坞一座。第三期新建200米x 35米X10米干船坞和200 米x 50米X10米干船坞各一座，并完善扩大船舶建造和修理能力所需的配套生产设施、设备、技术产权、管理体系。
New yards Aker Finnyards OY Aker Brattvaag AS Aker MTW GmBH Langsten Slip og Båtbyggeri Aukra Industrier AS

工程项目管理大纲(新版)

课程简介课程号：课程名称：建设工程项目管理英文名称周学时：4.0-0.0 学分：预修要求：内容简介：本课程将通过课堂讲授和大型作业，使学生系统的了解、熟悉、掌握建筑施工项目管理的基本内容、基本程序和基本方法，掌握建筑工程项目从招标开始到竣工保修全过程中各阶段的管理实施方案。

把学生培养成懂管理、会算账、知行情、懂技术、肯吃苦、善公关的现代管理人才。

选用教材或参考书：1、选用教材：《建筑工程项目管理》罗定伦上海交通大学出版社2014版2、参考教材：高等院校同类专业的师生和管理人员学习参考书。

《建筑工程项目管理》教学大纲一、课程的教学目的和基本要求教学目的：通过本课程教学，使学生掌握建设工程项目管理管理所涉及的基本概念、基本原理、基本知识和职业岗位技能。

在教学过程中，有关的知识体系按不同程度分三个层次做出要求。

基本要求：（1）了解：要求学员知道这部分内容。

（2）熟悉：要求学员对这部分内容能够理解。

(3）掌握：要求学员对这部分内容能够深入理解并熟练掌握.(4)能将所学知识应用到实践当中。

二、相关教学环节安排1．采用多媒体投影教学。

2．习题课单列，每周4学时。

三、课程主要内容及学时分配每周4学时，共8周。

主要内容：(一)课程导入1学时(二)管理的一般概念3学时1. 管理概述1学时2．项目管理1学时3．建设工程施工项目管理的组织1学时(三)建设工程施工项目的生产要素管理5学时1．施工人员的管理1学时2. 建设工程项目施工材料管理1学时3. 施工机械设备管理1学时4．施工项目技术管理1学时5. 施工项目资金管理1学时(四)建设工程施工项目安全管理3学时1．施工项目安全管理概述1学时2．施工现场安全管理1学时3．施工安全事故处理1学时(五)建设工程施工质量控制5学时1．施工质量管理与施工质量控制1学时2．施工质量管理体系1学时3．施工质量控制的内容和方法1学时4. 施工质量事故预防与处理1学时5. 施工质量的政府监督1学时(六)建设工程施工项目进度控制4学时1．建设工程项目进度控制1学时2．工程项目进度计划的编制1学时3．工程项目进度计划的实施1学时4. 工程项目进度计划的检查、调整与控制1学时(七)建设工程施工项目成本控制4学时1．建筑安装工程费的组成1学时2. 建筑安装工程费用计算方法及计价程序1学时3．施工成本控制的步骤及方法1学时4. 施工成本核算和分析1学时（八）建设工程施工合同管理7学时1. 建设工程施工合同管理概述1学时2.建设工程施工招标和投标1学时3.建设工程施工承发包模式1学时4.建设工程施工合同与物质采购合同的内容1学时5.建设工程施工合同计价方式1学时6.建设工程施工合同执行过程中的管理1学时7.建设工程施工索赔1学时（九）建设工程施工风险管理与沟通管理2学时1.施工风险管理1学时2.建筑工程项目沟通管理 1 学时（十）工程项目收尾管理2学时1.工程项目竣工验收1学时2.工程项目产品回访与保修1学时（十一）建设工程技术资料管理2学时1.建设工程项目资料管理概述1学时2.建设工程资料的归档及整理1学时（十二）工程项目监理制度 2 学时1.工程项目监理制度概述1学时2..建设工程施工阶段的监理程序1学时四、教材及主要参考书教材：建筑工程项目管理参考书目::《设工程监理概论.》、《建设工程施工管理》、《建设工程项目管理》、《建设工程造价管理》等。

项目管理计划英文

项目管理计划英文 SANY标准化小组 #QS8QHH-HHGX8Q8-GNHHJ8-HHMHGN#<Project Name>Project Management PlanVersion <>[Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.][State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]Table of Contents1. Introduction 5Purpose 5Scope 5Definitions, Acronyms and Abbreviations 5References 5Overview 5 2. Project Overview 6Project Name, Code and Leader 6Project Purpose, Scope and Objectives 6Assumptions and Constraints 6 Critical Assumptions and Constraints 6Non-Critical Assumptions and Constraints 6 Project Milestones 6Project Deliverables 6Tailoring Guidelines 6Software Development Life Cycle 7 3. Project Organization 8Organizational Structure 8External Interfaces 10Roles and Responsibilities 10 <Organizational Unit Name> 10 4. Management Process 11Work Breakdown Structure (WBS) 11Project Estimates 11 Estimation Technique 11Size 11Effort 11Project Schedule 11 Pre-Development Schedule 11 Development Schedule 11 Project Phases, Iterations and Releases 11 Project Phases 11 Project Iterations 11 Releases 11 Project Resourcing 11 Staffing 11 Resource Acquisition 11 Training 12 Project Budget 12 Project Monitoring and Control 12 Schedule Control 12Budget Control 12Measurements 12 Risk Management Plan 12Project Closure 12 5. Technical Process Plans 13User Experience Design 13Requirements Management 13Analysis and Design 13Development Plan 13Peer Review Plan 13Project Maintenance 13Test Plan 13Tools, Techniques and Standards 13 Tools 13Techniques and Standards 14 Infrastructure 14Facilities 14Security Plan 14 6. Supporting Process Plans 15Configuration Management Plan 15Documentation 15Software Quality Assurance Plan 15Intergroup Coordination 15Communication 15Problem Resolution 15Subcontractor Management 157. Additional plans 168. Appendices 16Project Management Plan1.Introduction[The introduction of the Project Management Plan should provide an overview of the entire document. It should include the purpose,scope, definitions, acronyms, abbreviations, references andoverview of this Project Management Plan.]1.1Purpose[Specify the purpose of this Project Management Plan.]1.2Scope[A brief description of the scope of this Project Management Plan;what Project(s) it is associated with, and anything else that isaffected or influenced by this document.]1.3Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms,acronyms, and abbreviations required to interpret properly theProject Management Plan. This information may be provided byreference to the project Glossary.]1.4References[This subsection should provide a complete list of all documents referenced elsewhere in the Project Management Plan. Eachdocument should be identified by title, report number (ifapplicable), date, and publishing organization. Specify thesources from which the references can be obtained. Thisinformation may be provided by reference to an appendix or toanother document. For the Project Management Plan, the list of referenced artifacts may include:Risk Management PlanUser Interfaces GuidelinesConfiguration Management PlanSoftware Quality Assurance Plan, etc.]Document Title Publishing Organization<Title><Organization Name>1.5Overview[This subsection should describe what the rest of the Project Management Plan contains and explain how the document isorganized.]2.Project Overview2.1Project Name, Code and Leader[Specify the project name, project code and project leader(project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project,and a brief description of what deliverables the project isexpected to deliver.]2.3Assumptions and Constraints[A list of assumptions that this plan is based on, and anyconstraints . budget, staff, equipment, schedule, etc.) that apply to the project. Make a distinction between critical and non-critical factors.]2.3.1Critical Assumptions and Constraints[State the critical assumptions and constraints affecting theproject.]2.3.2Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4Project Milestones[Tabular list of major milestones to be achieved during theproject, with target dates.]2.5Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]2.6Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]3.Project Organization3.1Organizational Structure[Describe the organizational structure of the project team,including management and other review authorities. This shouldinclude identification of all project organizational units and a description of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:Project Implementation CommitteeProject Steering CommitteeProject Management TeamArchitecture GroupUser Experience Design TeamRequirements TeamAnalysis and Design TeamImplementation GroupDevelopment TeamDatabase Management TeamTesting TeamInfrastructure TeamConfiguration Management TeamSoftware Quality Assurance Team, etc.] Organizational Unit Description <Organizational Unit Name><Description>3.2External Interfaces[Describe how the project interfaces with external groups. Foreach external group, identify the internal/external contact names.]3.3Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.]3.3.1<Organizational Unit Name>4.Management Process4.1Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2Project Estimates4.2.1Estimation Technique[Specify the estimation method and the reason for its choice.Provide the estimated cost as well as the basis for thoseestimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2Size[State the size of each activity as calculated according to theestimation technique. Units of size may be in LOC, FP, etc.]4.2.3Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation. Units may be man-hours, man-days, etc.]4.3Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MSProject file.]4.3.1Pre-Development Schedule[This schedule will cater for project planning, requirements,analysis and design activities.]4.3.2Development Schedule[This schedule will cater coding, testing and deploymentactivities.]4.4Project Phases, Iterations and Releases4.4.1Project Phases[Identify phases and major milestones with their achievementcriteria.]4.4.2Project Iterations[Specify the number of iterations and list the objectives to beaccomplished for each of the iterations.]4.4.3Releases[Brief descriptions of each software release, whether demo, beta, etc.]4.5Project Resourcing4.5.1Staffing[Identify here the numbers and type of staff required (includingand special skills or experience), scheduled by project phase oriteration. State what resources are critical.]4.5.2Resource Acquisition[Describe how you will approach finding and acquiring the staffneeded for the project.]4.5.3Training[List any special training project team members will require, withtarget dates for when this training should be completed.]4.6Project Budget[Allocation of costs against the WBS and the project phases.]4.7Project Monitoring and Control4.7.1Schedule Control[Describes the approach to be taken to monitor progress againstthe planned schedule and how to take corrective action whenrequired.]4.7.2Budget Control[Describes the approach to be taken to monitor spending againstthe project budget and how to take corrective action whenrequired.]4.7.3Measurements[Describe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.]4.8Risk Management Plan[Enclosed by reference]4.9Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials,post-mortem debriefings and reports etc.]5.Technical Process Plans5.1User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.2Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.3Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.4Development Plan[Enclosed by reference]5.5Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6Maintenance[Describe details of any software maintenance for the warrantyperiod of the project.]5.7Test Plan[Enclosed by reference]5.8Tools, Techniques and Standards5.8.1Tools5.8.1.1Project Management Tools[Specify the project management tools that are to be used in theproject and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, projectmonitoring, status reporting, measurements, etc. Examples ofthese tools are MS Project, etc.]5.8.1.2Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issueresolution, requirement change management, measurements, etc.Examples of these tools are Rational Requisite Pro, EINS, etc.]5.8.1.3System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasons for their selection. Examples oftools in this area are Visio, Rational Rose, Power Designer etc.] 5.8.1.4Languages[Specify the languages that are to be used for softwaredevelopment in the project and the reasons for their selection.Examples of languages are HTML, Java, etc.]5.8.1.5User-Interface Development Tools[Specify the tools that are to be used for UI development in theproject and the reasons for their selection. Examples of thesetools can be Dreamweaver, Flash, etc.]5.8.1.6Database Management System Software[Specify the database management system software that is to beused in the project and the reasons for their selection. Examplesof these tools are Oracle, SQL Server, etc.]5.8.1.7Third Party Software[Specify any third party software that is to be used in theproject and the reasons for their selection. Examples are Inktomi, Infranet, etc.]5.8.1.8Software Testing Tools[Specify the software testing tools that are to be used in theproject and the reasons for their selection. Examples of thesetools are WinRunner, LoadRunner, etc.]5.8.1.9Defect and Change Management Tools[Specify the defect and change management tools that are to beused in the project and the reasons for their selection. Examplesof these tools are ClearQuest, etc.]5.8.1.10Configuration Management Tools[Specify the configuration management tools that are to be used in the project and the reasons for their selection. Examples ofthese tools are ClearCase, etc.]5.8.1.11Integrated Development Environment[Specify the operating systems (platforms), web servers,application servers, development servers that are to be used inthe project and the reasons for their selection. Examples ofthese tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.]5.8.2Techniques and Standards[Lists the documented project technical standards etc by reference.Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]5.9Infrastructure[Specify hardware, network connectivity, bandwidth, etc., requiredin this project. Make a clear distinction about what factors arecritical.]5.10Facilities[Describe the facilities required for the execution of the project.This will cover physical workspace, buildings, etc.]5.11Security Plan[List down the security consideration . of security can beoperating system, access controls to site/product, physicalsecurity considerations.]6.Supporting Process Plans6.1Configuration Management Plan[Enclosed by reference]6.2Documentation[Specify the documents that will be produced in the project, whatdocument templates will be used, and any other informationpertaining to documentation.]6.3Software Quality Assurance Plan[Enclosed by reference]6.4Intergroup Coordination[Describe how different project groups will communicate with oneanother; specify dependencies, and commitments.]6.5Communication[Specify how various workers/units/entities, both within andoutside the project team, will communicate with each other.]6.6Problem Resolution[Describe the approach for resolving issues in the project,escalation procedures, etc.]6.7Subcontractor Management[If subcontractors are involved in the project give details ofwhat kind of contractors are required for various tasks, theduration for which they are required and how they will be managed.]7.Additional plans[Additional plans if required by contract or regulations.] 8.Appendices[Attach any supplementary information.]。

(项目管理)项目管理计划模板(英文)

<Project Name>Project Management PlanVersion <x.x> [Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.]Distribution List[State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]Table of Contents1.Introduction 51.1Purpose 51.2Scope 51.3Definitions, Acronyms and Abbreviations 51.4References 51.5Overview 52.Project Overview 62.1Project Name, Code and Leader 62.2Project Purpose, Scope and Objectives 62.3Assumptions and Constraints 62.3.1Critical Assumptions and Constraints 62.3.2Non-Critical Assumptions and Constraints 62.4Project Milestones 62.5Project Deliverables 62.6Tailoring Guidelines 72.7Software Development Life Cycle 73.Project Organization 83.1Organizational Structure 83.2External Interfaces 103.3Roles and Responsibilities 103.3.1<Organizational Unit Name> 104.Management Process 114.1Work Breakdown Structure (WBS) 114.2Project Estimates 114.2.1Estimation Technique 114.2.2Size 114.2.3Effort 114.3Project Schedule 114.3.1Pre-Development Schedule 114.3.2Development Schedule 114.4Project Phases, Iterations and Releases 114.4.1Project Phases 114.4.2Project Iterations 114.4.3Releases 114.5Project Resourcing 114.5.1Staffing 114.5.2Resource Acquisition 124.5.3Training 124.6Project Budget 124.7Project Monitoring and Control 124.7.1Schedule Control 124.7.2Budget Control 124.7.3Measurements 124.8Risk Management Plan 124.9Project Closure 125.Technical Process Plans 135.1User Experience Design 135.2Requirements Management 135.3Analysis and Design 135.4Development Plan 135.5Peer Review Plan 135.6Project Maintenance 135.7Test Plan 135.8Tools, Techniques and Standards 135.8.1Tools 135.8.2Techniques and Standards 145.9Infrastructure 145.10Facilities 145.11Security Plan 146.Supporting Process Plans 156.1Configuration Management Plan 156.2Documentation 156.3Software Quality Assurance Plan 156.4Intergroup Coordination 156.5Communication 156.6Problem Resolution 156.7Subcontractor Management 157.Additional plans 168.Appendices 16Project Management Plan1. Introduction[The introduction of the Project Management Plan should provide an overview of the entiredocument. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]1.1 Purpose[Specify the purpose of this Project Management Plan.]1.2 Scope[A brief description of the scope of this Project Management Plan; what Project(s) it isassociated with, and anything else that is affected or influenced by this document.]1.3 Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms, acronyms, and abbreviationsrequired to interpret properly the Project Management Plan. This information may be provided by reference to the project Glossary.]1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in theProject Management Plan. Each document should be identified by title, report number (ifapplicable), date, and publishing organization. Specify the sources from which the referencescan be obtained. This information may be provided by reference to an appendix or to anotherdocument. For the Project Management Plan, the list of referenced artifacts may include:•Risk Management Plan•User Interfaces Guidelines•Configuration Management Plan•Software Quality Assurance Plan, etc.]1.5 Overview[This subsection should describe what the rest of the Project Management Plan contains andexplain how the document is organized.]2. Project Overview2.1 Project Name, Code and Leader[Specify the project name, project code and project leader (project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2 Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expected to deliver.]2.3 Assumptions and Constraints[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project. Make a distinction between critical and non-criticalfactors.]2.3.1 Critical Assumptions and Constraints[State the critical assumptions and constraints affecting the project.]2.3.2 Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4 Project Milestones[Tabular list of major milestones to be achieved during the project, with target dates.]2.5 Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]2.6 Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7 Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]3. Project Organization3.1 Organizational Structure[Describe the organizational structure of the project team, including management and otherreview authorities. This should include identification of all project organizational units and adescription of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:•Project Implementation Committee•Project Steering Committee•Project Management Team•Architecture Group•User Experience Design Team•Requirements Team•Analysis and Design Team•Implementation Group•Development Team•Database Management Team•Testing Team•Infrastructure Team•Configuration Management Team•Software Quality Assurance Team, etc.]3.2 External Interfaces[Describe how the project interfaces with external groups. For each external group, identify the internal/external contact names.]3.3 Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.] 3.3.1 <Organizational Unit Name>4. Management Process4.1 Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2 Project Estimates4.2.1 Estimation Technique[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as the basis for those estimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2 Size[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]4.2.3 Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation.Units may be man-hours, man-days, etc.]4.3 Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points,demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]4.3.1 Pre-Development Schedule[This schedule will cater for project planning, requirements, analysis and design activities.]4.3.2 Development Schedule[This schedule will cater coding, testing and deployment activities.]4.4 Project Phases, Iterations and Releases4.4.1 Project Phases[Identify phases and major milestones with their achievement criteria.]4.4.2 Project Iterations[Specify the number of iterations and list the objectives to be accomplished for each of theiterations.]4.4.3 Releases[Brief descriptions of each software release, whether demo, beta, etc.]4.5 Project Resourcing4.5.1 Staffing[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]4.5.2 Resource Acquisition[Describe how you will approach finding and acquiring the staff needed for the project.]4.5.3 Training[List any special training project team members will require, with target dates for when thistraining should be completed.]4.6 Project Budget[Allocation of costs against the WBS and the project phases.]4.7 Project Monitoring and Control4.7.1 Schedule Control[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]4.7.2 Budget Control[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]4.7.3 Measurements[Describe the types of measurements to be taken, their frequency, and responsibleworkers/entities for this purpose.]4.8 Risk Management Plan[Enclosed by reference]4.9 Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]5. Technical Process Plans5.1 User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.2 Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.3 Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.4 Development Plan[Enclosed by reference]5.5 Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6 Maintenance[Describe details of any software maintenance for the warranty period of the project.]5.7 Test Plan[Enclosed by reference]5.8 Tools, Techniques and Standards5.8.1 Tools5.8.1.1 Project Management Tools[Specify the project management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, projectmonitoring, status reporting, measurements, etc. Examples of these tools are MS Project, etc.]5.8.1.2 Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issueresolution, requirement change management, measurements, etc. Examples of these tools areRational Requisite Pro, EINS, etc.]5.8.1.3 System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasonsfor their selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]5.8.1.4 Languages[Specify the languages that are to be used for software development in the project and thereasons for their selection. Examples of languages are HTML, Java, etc.]5.8.1.5 User-Interface Development Tools[Specify the tools that are to be used for UI development in the project and the reasons for their selection. Examples of these tools can be Dreamweaver, Flash, etc.]5.8.1.6 Database Management System Software[Specify the database management system software that is to be used in the project and thereasons for their selection. Examples of these tools are Oracle, SQL Server, etc.]5.8.1.7 Third Party Software[Specify any third party software that is to be used in the project and the reasons for theirselection. Examples are Inktomi, Infranet, etc.]5.8.1.8 Software Testing Tools[Specify the software testing tools that are to be used in the project and the reasons for theirselection. Examples of these tools are WinRunner, LoadRunner, etc.]5.8.1.9 Defect and Change Management Tools[Specify the defect and change management tools that are to be used in the project and thereasons for their selection. Examples of these tools are ClearQuest, etc.]5.8.1.10 Configuration Management Tools[Specify the configuration management tools that are to be used in the project and the reasonsfor their selection. Examples of these tools are ClearCase, etc.]5.8.1.11 Integrated Development Environment[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.]5.8.2 Techniques and Standards[Lists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]5.9 Infrastructure[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]5.10 Facilities[Describe the facilities required for the execution of the project. This will cover physicalworkspace, buildings, etc.]5.11 Security Plan[List down the security consideration e.g. of security can be operating system, access controls to site/product, physical security considerations.]6. Supporting Process Plans6.1 Configuration Management Plan[Enclosed by reference]6.2 Documentation[Specify the documents that will be produced in the project, what document templates will beused, and any other information pertaining to documentation.]6.3 Software Quality Assurance Plan[Enclosed by reference]6.4 Intergroup Coordination[Describe how different project groups will communicate with one another; specify dependencies, and commitments.]6.5 Communication[Specify how various workers/units/entities, both within and outside the project team, willcommunicate with each other.]6.6 Problem Resolution[Describe the approach for resolving issues in the project, escalation procedures, etc.]6.7 Subcontractor Management[If subcontractors are involved in the project give details of what kind of contractors are required for various tasks, the duration for which they are required and how they will be managed.]7. Additional plans[Additional plans if required by contract or regulations.] 8. Appendices[Attach any supplementary information.]。

项目管理模板英文版ProjectManagement

Project Control Improper
Planning for
3
16.7%
IM_RC11
apacity Not Meet
Engineering
Coding
Methods
0
0.0%
Standard
Pபைடு நூலகம்_RC4
PN_RC5 PN_RC6
PN_RC7
PN_RC8
Roles WBS Risk/dependen cy Tailored Process
200
15.4
20,000
10,000
1,666.7
Total
1,682.1 FP
Overall #DIV/0! FP/Person-
Productivity
days
Size & Productivity Analysis:
Findings
Recommendations
Cost:
Description
tion
5
27.8%
IM_RC1 IM_RC2
Not meet Design/Require ment
RM_RC3 RM_RC4 RM_RC5
ble Risk/dependen cy Missing/Unclear /Incorrect
Traceability
0
0.0%
0
0.0%
0
0.0%
5
27.8%
Planning Phase
Requirement Design Phase Implementatio Testing Phase Release Phase
Phase

项目管理计划模板(英文doc 6页)

<Project Name>Project Management PlanVersion <x.x> [Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.][State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]Table of Contents1.Introduction1.1Purpose1.2Scope1.3Definitions, Acronyms and Abbreviations1.4References1.5Overview2.Project Overview2.1Project Name, Code and Leader2.2Project Purpose, Scope and Objectives2.3Assumptions and Constraints2.3.1Critical Assumptions and Constraints2.3.2Non-Critical Assumptions and Constraints2.4Project Milestones2.5Project Deliverables2.6Tailoring Guidelines2.7Software Development Life Cycle3.Project Organization3.1Organizational Structure3.2External Interfaces3.3Roles and Responsibilities3.3.1<Organizational Unit Name>4.Management Process4.1Work Breakdown Structure (WBS)4.2Project Estimates4.2.1Estimation Technique4.2.2Size4.2.3Effort4.3Project Schedule4.3.1Pre-Development Schedule4.3.2Development Schedule4.4Project Phases, Iterations and Releases4.4.1Project Phases4.4.2Project Iterations4.4.3Releases4.5Project Resourcing4.5.1Staffing4.5.2Resource Acquisition4.5.3Training4.6Project Budget4.7Project Monitoring and Control4.7.1Schedule Control4.7.2Budget Control4.7.3Measurements4.8Risk Management Plan4.9Project Closure5.Technical Process Plans5.1User Experience Design5.2Requirements Management5.3Analysis and Design5.4Development Plan5.5Peer Review Plan5.6Project Maintenance5.7Test Plan5.8Tools, Techniques and Standards5.8.1Tools5.8.2Techniques and Standards5.9Infrastructure5.10Facilities5.11Security Plan6.Supporting Process Plans6.1Configuration Management Plan6.2Documentation6.3Software Quality Assurance Plan6.4Intergroup Coordination6.5Communication6.6Problem Resolution6.7Subcontractor Management7.Additional plans8.AppendicesProject Management Plan1. Introduction[The introduction of the Project Management Plan should provide an overview of the entiredocument. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]1.1 Purpose[Specify the purpose of this Project Management Plan.]1.2 Scope[A brief description of the scope of this Project Management Plan; what Project(s) it isassociated with, and anything else that is affected or influenced by this document.]1.3 Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms, acronyms, and abbreviationsrequired to interpret properly the Project Management Plan.? This information may be provided by reference to the project Glossary.]1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in theProject Management Plan. Each document should be identified by title, report number (ifapplicable), date, and publishing organization. Specify the sources from which the referencescan be obtained. This information may be provided by reference to an appendix or to anotherdocument. For the Project Management Plan, the list of referenced artifacts may include:∙Risk Management Plan∙User Interfaces Guidelines∙Configuration Management Plan∙Software Quality Assurance Plan, etc.]1.5 Overview[This subsection should describe what the rest of the Project Management Plan contains andexplain how the document is organized.]2. Project Overview2.1 Project Name, Code and Leader[Specify the project name, project code and project leader (project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2 Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expected to deliver.]2.3 Assumptions and Constraints[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project. Make a distinction between critical and non-criticalfactors.]2.3.1 Critical Assumptions and Constraints[State the critical assumptions and constraints affecting the project.]2.3.2 Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4 Project Milestones[Tabular list of major milestones to be achieved during the project, with target dates.]2.5 Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]2.6 Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7 Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]3. Project Organization3.1 Organizational Structure[Describe the organizational structure of the project team, including management and otherreview authorities. This should include identification of all project organizational units and adescription of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:∙Project Implementation Committee∙Project Steering Committee∙Project Management Team∙Architecture Group∙User Experience Design Team∙Requirements Team∙Analysis and Design Team∙Implementation Group∙Development Team∙Database Management Team∙Testing Team∙Infrastructure Team∙Configuration Management Team∙Software Quality Assurance Team, etc.]3.2 External Interfaces[Describe how the project interfaces with external groups. For each external group, identify the internal/external contact names.]3.3 Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.] 3.3.1 <Organizational Unit Name>4. Management Process4.1 Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2 Project Estimates4.2.1 Estimation Technique[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as the basis for those estimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2 Size[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]4.2.3 Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation.Units may be man-hours, man-days, etc.]4.3 Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points,demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]4.3.1 Pre-Development Schedule[This schedule will cater for project planning, requirements, analysis and design activities.]4.3.2 Development Schedule[This schedule will cater coding, testing and deployment activities.]4.4 Project Phases, Iterations and Releases4.4.1 Project Phases[Identify phases and major milestones with their achievement criteria.]4.4.2 Project Iterations[Specify the number of iterations and list the objectives to be accomplished for each of theiterations.]4.4.3 Releases[Brief descriptions of each software release, whether demo, beta, etc.]4.5 Project Resourcing4.5.1 Staffing[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]4.5.2 Resource Acquisition[Describe how you will approach finding and acquiring the staff needed for the project.]4.5.3 Training[List any special training project team members will require, with target dates for when thistraining should be completed.]4.6 Project Budget[Allocation of costs against the WBS and the project phases.]4.7 Project Monitoring and Control4.7.1 Schedule Control[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]4.7.2 Budget Control[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]4.7.3 Measurements[Describe the types of measurements to be taken, their frequency, and responsibleworkers/entities for this purpose.]4.8 Risk Management Plan[Enclosed by reference]4.9 Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]5. Technical Process Plans5.1 User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.2 Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.3 Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to be followed.]5.4 Development Plan[Enclosed by reference]5.5 Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6 Maintenance[Describe details of any software maintenance for the warranty period of the project.]5.7 Test Plan[Enclosed by reference]5.8 Tools, Techniques and Standards5.8.1 Tools5.8.1.1 Project Management Tools[Specify the project management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are project planning, project scheduling, projectmonitoring, status reporting, measurements, etc. Examples of these tools are MS Project, etc.]5.8.1.2 Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for their selection. Examples of areas to be covered are requirements gathering, requirement issueresolution, requirement change management, measurements, etc. Examples of these tools areRational Requisite Pro, EINS, etc.]5.8.1.3 System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasonsfor their selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]5.8.1.4 Languages[Specify the languages that are to be used for software development in the project and thereasons for their selection. Examples of languages are HTML, Java, etc.]5.8.1.5 User-Interface Development Tools[Specify the tools that are to be used for UI development in the project and the reasons for their selection. Examples of these tools can be Dreamweaver, Flash, etc.]5.8.1.6 Database Management System Software[Specify the database management system software that is to be used in the project and thereasons for their selection. Examples of these tools are Oracle, SQL Server, etc.]5.8.1.7 Third Party Software[Specify any third party software that is to be used in the project and the reasons for theirselection. Examples are Inktomi, Infranet, etc.]5.8.1.8 Software Testing Tools[Specify the software testing tools that are to be used in the project and the reasons for theirselection. Examples of these tools are WinRunner, LoadRunner, etc.]5.8.1.9 Defect and Change Management Tools[Specify the defect and change management tools that are to be used in the project and thereasons for their selection. Examples of these tools are ClearQuest, etc.]5.8.1.10 C onfiguration Management Tools[Specify the configuration management tools that are to be used in the project and the reasonsfor their selection. Examples of these tools are ClearCase, etc.]5.8.1.11 I ntegrated Development Environment[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris, iPlanet, JBuilder, WebSphere, etc.]5.8.2 Techniques and Standards[Lists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]5.9 Infrastructure[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]5.10 Facilities[Describe the facilities required for the execution of the project. This will cover physicalworkspace, buildings, etc.]5.11 Security Plan[List down the security consideration e.g. of security can be operating system, access controls to site/product, physical security considerations.]6. Supporting Process Plans6.1 Configuration Management Plan[Enclosed by reference]6.2 Documentation[Specify the documents that will be produced in the project, what document templates will beused, and any other information pertaining to documentation.]6.3 Software Quality Assurance Plan[Enclosed by reference]6.4 Intergroup Coordination[Describe how different project groups will communicate with one another; specify dependencies, and commitments.]6.5 Communication[Specify how various workers/units/entities, both within and outside the project team, willcommunicate with each other.]6.6 Problem Resolution[Describe the approach for resolving issues in the project, escalation procedures, etc.]6.7 Subcontractor Management[If subcontractors are involved in the project give details of what kind of contractors are required for various tasks, the duration for which they are required and how they will be managed.]7. Additional plans[Additional plans if required by contract or regulations.] 8. Appendices[Attach any supplementary information.]。

项目管理模板(英文)

Prioritization Matrix Project Name:Date:PROJECT STATEMENT OF WORK Project Name:Project Sponsor:Project Start Date:Project Charter Approval – The signatures below represent approval for this project as chartered in this document. The people signing below must approve in writing changes to the scope, objectives, constraints, key success measures or key assumptions prior to implementing those changes__________________________ __________ __________________________ _______ Signature Date Signature Date__________________________ __________ __________________________ _______ Signature Date Signature Date__________________________ __________ __________________________ _______ Signature Date Signature DatePROJECT STATUS REPORT EXAMPLE Project Name: Jax, FL #2Project Manager: Mandy DietzProject Sponsor: Jim ChampionStatus as of: 07/26/99I.SCHEDULEI.BUDGETActual To Date: $ 27,000Projected Remaining Expenses: $473,000Projected Total: $500,000Budget: $525,000Projected Variance: ($25,000)II.SIGNIFICANT ACCOMPLISHMENTSClosed on purchase of property.Received final approval for store plans.New manager started full-time on July 13th.Reached agreement with lead construction company.Selected merchandise.I.UPCOMING DELIVERABLESComplete staffing assessmentPost for jobs internallyOrder merchandisePour foundationI.CRITICAL ISSUESThe lead construction contractor has indicated concern over finding adequate resources to meet our aggressive schedule. We should consider augmenting localresources with in-house construction team or back-up resources from alternatesource.City commissioners have just announced road construction work for the upcoming fiscal year. Plans call for widening of highway fronting the storelocation. We will need to determine timing and impact as it relates to storeopening and traffic.PROJECT SUMMARY AND ARCHIVAL PACKAGE Project Name:Project Sponsor:Project Manager:Project Start Date:Project Completion Date:__________________________ __________ __________________________ _______ Project Sponsor Date Project Manager Date Attachments:1.Project Charter2.Charter Modifications3.Updated Project Plan4.Status Reports5.Meeting Minutes6.Team Norms7.Contingency Plans8.Other Important Project Information。

项目管理各阶段的文档模版(汇总版)

项目可行性研究（模版1）一、项目基本情况项目名称: 制作日期：年月日制作人：签发人：二、项目背景1．目前状态（简要描述目前的商业环境和项目产生背景。

）2．拟解决的商业问题（简要说明需要项目解决的商业问题,以表明项目存在的理由.）3．影响范围（简要说明项目问题及问题的解决将对企业哪些方面产生影响，包括影响的组织范围。

）4．项目预期的结束日期（尽可能对项目的完成日期做出准确推断.）三、可能的项目方案方案1：(对第三部分提出的若干项目方案进行评估，并提出推荐意见。

在一件重要说明各种方案可能的风险以及修正或调节意见。

）对各方案的结论：□接受□拒绝□修改□暂缓决定五、签字(由项目可行性论证小组成员签字,项目组成员至少需要包含商业/管理、财务、技术三方面的人员.）项目描述(模版2）一、项目基本情况项目名称：制作日期：年月日制作人：签发人：二、项目目的1．项目需解决的商业问题(所有的项目均起始于某个商业问题，该部分简要描述这些问题.）2．项目工作内容（对项目范围的限定，以及对完成项目的主要工作内容和方法的陈述。

）3．项目目标(包含工期目标、费用目标和交付产品特征与特征的主要描述.)三、项目的关键成功要素(对确保项目成功的关键环节和关键资源、关键方法、度量标准等进行概念性地简要描述。

）四、项目影响范围(包含对企业战略的影响、对技术的影响和对财务的影响.）五、项目主要里程碑计划（包含主要里程碑的时间、费用和成果目标。

）六、项目假设（说明项目的主要假设条件.）七、项目约束条件(说明项目启动和实施过程中的限制性条件。

）八、项目评价标准(说明项目成果在何种情况下将被接受，何时项目将被终止或取消，项目成功标准的度量或验收规程.）九、项目主要利益相关者（包括项目发起人，项目经理，项目团队主要成员，相关职能部门负责人,客户等的头衔、签字和签字日期.）项目章程(模版3）一、项目基本情况项目名称：制作日期：年月日制作人: 签发人：二、项目目的（简要说明项目的目的和本项目章程的目的。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

<Project Name>Project Management PlanVersion <x.x>[Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.]Distribution List[State the persons/teams/groups to whom this document should be distributed whenever the document is revised. Also state the name of their parent organization.]Table of Contents1.Introduction 51.1Purpose 51.2Scope 51.3Definitions, Acronyms and Abbreviations 51.4References 51.5Overview 52.Project Overview 62.1Project Name, Code and Leader 62.2Project Purpose, Scope and Objectives 62.3Assumptions and Constraints 62.3.1Critical Assumptions and Constraints 62.3.2Non-Critical Assumptions and Constraints 62.4Project Milestones 62.5Project Deliverables 62.6Tailoring Guidelines 62.7Software Development Life Cycle 73.Project Organization 83.1Organizational Structure 83.2External Interfaces 103.3Roles and Responsibilities 103.3.1<Organizational Unit Name> 104.Management Process 114.1Work Breakdown Structure (WBS) 114.2Project Estimates 114.2.1Estimation Technique 114.2.2Size 114.2.3Effort 114.3Project Schedule 114.3.1Pre-Development Schedule 114.3.2Development Schedule 114.4Project Phases, Iterations and Releases 114.4.1Project Phases 114.4.2Project Iterations 114.4.3Releases 114.5Project Resourcing 114.5.1Staffing 114.5.2Resource Acquisition 114.5.3Training 114.6Project Budget 124.7Project Monitoring and Control 124.7.1Schedule Control 124.7.2Budget Control 124.7.3Measurements 124.8Risk Management Plan 124.9Project Closure 125.Technical Process Plans 135.1User Experience Design 135.2Requirements Management 135.3Analysis and Design 135.4Development Plan 135.5Peer Review Plan 135.6Project Maintenance 135.7Test Plan 135.8Tools, Techniques and Standards 135.8.1Tools 135.8.2Techniques and Standards 145.9Infrastructure 145.10Facilities 145.11Security Plan 146.Supporting Process Plans 156.1Configuration Management Plan 156.2Documentation 156.3Software Quality Assurance Plan 156.4Intergroup Coordination 156.5Communication 156.6Problem Resolution 156.7Subcontractor Management 157.Additional plans 168.Appendices 16Project Management Plan1. Introduction[The introduction of the Project Management Plan should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]1.1 Purpose[Specify the purpose of this Project Management Plan.]1.2 Scope[A brief description of the scope of this Project Management Plan; what Project(s) it is associated with,and anything else that is affected or influenced by this document.]1.3 Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms, acronyms, and abbreviations required tointerpret properly the Project Management Plan. This information may be provided by reference to the project Glossary.]1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in the ProjectManagement Plan. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document. For the Project Management Plan, the list of referenced artifacts may include:•Risk Management Plan•User Interfaces Guidelines•Configuration Management Plan•Software Quality Assurance Plan, etc.]1.5 Overview[This subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.]2. Project Overview2.1 Project Name, Code and Leader[Specify the project name, project code and project leader (project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2 Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expected to deliver.]2.3 Assumptions and Constraints[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project. Make a distinction between critical and non-critical factors.]2.3.1 Critical Assumptions and Constraints[State the critical assumptions and constraints affecting the project.]2.3.2 Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4 Project Milestones[Tabular list of major milestones to be achieved during the project, with target dates.]2.5 Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]2.6 Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7 Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]3. Project Organization3.1 Organizational Structure[Describe the organizational structure of the project team, including management and other reviewauthorities. This should include identification of all project organizational units and a description of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:•Project Implementation Committee•Project Steering Committee•Project Management Team•Architecture Group•User Experience Design Team•Requirements Team•Analysis and Design Team•Implementation Group•Development Team•Database Management Team•Testing Team•Infrastructure Team•Configuration Management Team•Software Quality Assurance Team, etc.]3.2 External Interfaces[Describe how the project interfaces with external groups. For each external group, identify theinternal/external contact names.]3.3 Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.] 3.3.1 <Organizational Unit Name>4. Management Process4.1 Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2 Project Estimates4.2.1 Estimation Technique[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as thebasis for those estimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2 Size[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]4.2.3 Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation. Unitsmay be man-hours, man-days, etc.]4.3 Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]4.3.1 Pre-Development Schedule[This schedule will cater for project planning, requirements, analysis and design activities.]4.3.2 Development Schedule[This schedule will cater coding, testing and deployment activities.]4.4 Project Phases, Iterations and Releases4.4.1 Project Phases[Identify phases and major milestones with their achievement criteria.]4.4.2 Project Iterations[Specify the number of iterations and list the objectives to be accomplished for each of the iterations.]4.4.3 Releases[Brief descriptions of each software release, whether demo, beta, etc.]4.5 Project Resourcing4.5.1 Staffing[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]4.5.2 Resource Acquisition[Describe how you will approach finding and acquiring the staff needed for the project.]4.5.3 Training[List any special training project team members will require, with target dates for when this trainingshould be completed.]4.6 Project Budget[Allocation of costs against the WBS and the project phases.]4.7 Project Monitoring and Control4.7.1 Schedule Control[Describes the approach to be taken to monitor progress against the planned schedule and how to takecorrective action when required.]4.7.2 Budget Control[Describes the approach to be taken to monitor spending against the project budget and how to takecorrective action when required.]4.7.3 Measurements[Describe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.]4.8 Risk Management Plan[Enclosed by reference]4.9 Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]5. Technical Process Plans5.1 User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.2 Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.3 Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.4 Development Plan[Enclosed by reference]5.5 Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6 Maintenance[Describe details of any software maintenance for the warranty period of the project.]5.7 Test Plan[Enclosed by reference]5.8 Tools, Techniques and Standards5.8.1 Tools5.8.1.1 Project Management Tools[Specify the project management tools that are to be used in the project and the reasons for their selection.Examples of areas to be covered are project planning, project scheduling, project monitoring, statusreporting, measurements, etc. Examples of these tools are MS Project, etc.]5.8.1.2 Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for theirselection. Examples of areas to be covered are requirements gathering, requirement issue resolution,requirement change management, measurements, etc. Examples of these tools are Rational Requisite Pro, EINS, etc.]5.8.1.3 System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasons for theirselection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]5.8.1.4 Languages[Specify the languages that are to be used for software development in the project and the reasons for their selection. Examples of languages are HTML, Java, etc.]5.8.1.5 User-Interface Development Tools[Specify the tools that are to be used for UI development in the project and the reasons for their selection.Examples of these tools can be Dreamweaver, Flash, etc.]5.8.1.6 Database Management System Software[Specify the database management system software that is to be used in the project and the reasons fortheir selection. Examples of these tools are Oracle, SQL Server, etc.]5.8.1.7 Third Party Software[Specify any third party software that is to be used in the project and the reasons for their selection.Examples are Inktomi, Infranet, etc.]5.8.1.8 Software Testing Tools[Specify the software testing tools that are to be used in the project and the reasons for their selection.Examples of these tools are WinRunner, LoadRunner, etc.]5.8.1.9 Defect and Change Management Tools[Specify the defect and change management tools that are to be used in the project and the reasons fortheir selection. Examples of these tools are ClearQuest, etc.]5.8.1.10 Configuration Management Tools[Specify the configuration management tools that are to be used in the project and the reasons for theirselection. Examples of these tools are ClearCase, etc.]5.8.1.11 Integrated Development Environment[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris,iPlanet, JBuilder, WebSphere, etc.]5.8.2 Techniques and Standards[Lists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]5.9 Infrastructure[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]5.10 Facilities[Describe the facilities required for the execution of the project. This will cover physical workspace,buildings, etc.]5.11 Security Plan[List down the security consideration e.g. of security can be operating system, access controls tosite/product, physical security considerations.]6. Supporting Process Plans6.1 Configuration Management Plan[Enclosed by reference]6.2 Documentation[Specify the documents that will be produced in the project, what document templates will be used, and any other information pertaining to documentation.]6.3 Software Quality Assurance Plan[Enclosed by reference]6.4 Intergroup Coordination[Describe how different project groups will communicate with one another; specify dependencies, andcommitments.]6.5 Communication[Specify how various workers/units/entities, both within and outside the project team, will communicatewith each other.]6.6 Problem Resolution[Describe the approach for resolving issues in the project, escalation procedures, etc.]6.7 Subcontractor Management[If subcontractors are involved in the project give details of what kind of contractors are required forvarious tasks, the duration for which they are required and how they will be managed.]7. Additional plans[Additional plans if required by contract or regulations.]8. Appendices[Attach any supplementary information.]。