Scope-Management-Plan
- 格式:doc
- 大小:141.00 KB
- 文档页数:10
实际成本2. ACWP已完工作实际成本3. BAC完工预算4. CCB变更控制委员会5. COQ质量成本6. CPAF成本加奖励费用合同7. CPFF成本加固定费用合同8. CPI成本绩效指数9. CPIF成本加激励费用合同10. CPM关键路径法11. CV成本偏差12. EAC完工估算13. EF最早完成日期14. EMV预期货币价值15. ES最早开始日期16. ETC完工尚需估算17. EV挣值18. EVM挣值管理19. FF完成到完成20. FFP固定总价合同21. FMEA失效模式与影响分析22. FP-EPA总价加经济价格调整合同总价加激励费用合同24. FS完成到开始25. IFB投标邀请书26. LF最晚完成日期27. LOE支持型活动28. LS最晚开始日期29. OBS组织分解结构30. PDM紧前关系绘图法31. PMBOK项目管理知识体系32. PV计划价值33. QFD质量功能展开34. RACIRACI:责任分配矩阵的一种常见类型,使用执行、负责、咨询和知情等词语来定义干系人在项目活动中的参与状态。
35. RAM责任分配矩阵36. RBS风险分解结构37. RFI信息邀请书38. RFP建议邀请书39. RFQ报价邀请书40. SF开始到完成41. SOW工作说明书42. SPI进度绩效指数43. SS开始到开始44. SV进度偏差45. SWOT优势、劣势、机会与威胁46. TM工料47. WBS工作分解结构48. SWOT AnalysisSWOT分析对一个组织、项目或备选方案的优势、劣势、机会和威胁的分析。
49. Performance Reporting报告绩效见“工作绩效报告”。
50. Reporting Systems报告系统用于从一个或多个信息管理系统中生成或合并报告,并向项目干系人发送报告的设施、过程和程序。
51. Request for Quotation (RFQ)报价邀请书采购文件的一种,用来向潜在卖方征求对通用或标准产品或服务的报价。
5.Scope ManagementScope Management-the process of defining what work is required-make sure all of that work and ONLY that work is done (O.W. Gold Plating)-generally an easy topicProduct Scope vs Project ScopeProduct Scope: measure against product requirementProject Scope: measure against project planScope Management Plan-how scope will be planned, executed and controlled-it is created in Integration Management as a Subsidiary Plan of PM PlanCollect Requirement-Requirement: what stakeholder need from project/product-work should not be included just because someone want it-the high level requirement should already been defined in Project Charter, collect requirement involve gathering more specific I/P from all stakeholderGroup Creativity Technique-Brainstorming-Norminal Group Technique-Delphi Technique-Idea/Mind MapRequirement Documentation-Balancing stakeholder requirement-prioritize requirementDefine Scope-develop a detailed description of the projectProject Scope Statement-define project boundary-describe project deliverable and work required to create those deliverable-clearly define the project success criteriaManagement by Objective (MBO)- a management philosophy that says that organization should be managed by objective -MBO work best when it is supported by top managementCreate Work Breakdown Structure (WBS)-subdivide project deliverable into smaller, manageable component (work package)-Noted that NOT activity level <= Time Management-if it is not in WBS, it’s NOT part of the project-WBS does not show dependencyControl Account-management control pointWBS Dictionary-Description about WBS-can prevent scope creepScope Baseline= Project Scope Statement + WBS + WBS Dict.=> is a component of PM PlanVerify Scope-the process of frequent planned – in meeting with customer to gain formal acceptance of deliverable-verify scope is related to QC, diff. is that QC concern with correctness of deliverable, verify scope concern with acceptance of deliverable-QC usually done first, but can be in parallelControl Scope-measure scope performance and controlling change-ensure all change request, corrective action process through ICC-uncontrolled change => project scope creepGold - Plating-spending extra and unnecessary effort to make product perfect-it should be preventedITTOCollect RequirementDefine Scope (APEF)Create WBSVerify ScopeControl Scope1. Project Charter2. Stakeholder Register1. Interview2. Focus Group3. Facilitated Workshop4. Group Creativity Technique5. Group Decision Making Technique6. Questionnaire & Survey7. Observation8. Prototype1. Req. Doc2. Req. Mgt Plan3. Req. Traceability Matrix1. Project Charter2. Req. Doc1. Alternative Identification2. Product Analysis3. Expert Judgment4. Facilitated Workshop1. Project Scope Statement2. Project Doc. Update1. Project Scope Statement2. Req. DocDecomposition1. WBS2. WBS Dictionary3. Scope Baseline4. Project Doc. Update1. PM Plan2. Req. Doc3. Req. Traceability Matrix4. Validated DeliverableInspection1. Accepted Deliverable2. Change Request3. Project Doc. Update1. PM Plan2. Req. Doc3. Work Performance Info.4. Req. Traceability MatrixVariance Analysis1. Work Performance Measurement2. OPA Update3. Change Request4. PM Plan Update5. Project Doc. Update。
pmp49个过程PMP(Project Management Professional)认证是国际上认可的项目管理专业资格认证。
在项目管理中,有49个过程划分在5个过程组里。
这些过程和过程组应用于项目整个生命周期内,从项目启动到项目收尾。
通过了解这些过程和过程组,您可以更好地理解项目管理流程,加强项目管理技能。
下面我们将按照列表划分,对PMP的49个过程进行解读,内容通俗易懂。
1. 项目启动过程组(Initiating Process Group)项目启动过程组包含以下两个过程,涉及确定项目的业务需求和项目目标,执行合适的前期计划和项目授权,为成功实现项目奠定基础。
1.1 制定项目章程(Develop Project Charter)该过程定义项目,确定项目的上级,明确项目的目标、范围以及项目经理的职责。
该过程的输入包括商业文件、前期可行性研究、协议等。
输出包括项目章程、事业环境因素和组织过程资产更新。
1.2 辨识相关方(Identify Stakeholders)该过程旨在确定可能会受项目结果影响的各种利益相关方,并评估他们对项目的需求和期望。
该过程的输入包括工作绩效数据、商业文件、协议等。
输出是相关方登记册。
2. 规划过程组(Planning Process Group)规划过程组包含以下24个过程,涉及项目管理计划创建、任务分配、进度安排和成本管理等。
2.1 制定项目管理计划(Develop Project Management Plan)该过程开发项目管理计划,用来指导项目团队在后续执行过程中管理工作。
该过程的入口包括项目章程、商业文件等,输出包括项目管理计划。
2.2 确定项目范围(Define Scope)该过程明确项目的范围,阐述项目拟处理的产品和服务,所需的变更以及不包括的工作。
该过程的入口包括项目管理计划、项目章程等,输出包括项目范围说明书和验收准则。
2.3 制定项目范围计划(Create WBS)该过程将项目范围分解为一组由可管理的工作包组成的树形结构,以简化项目开发和实施的过程。
pmbok 项目经理职责英语The Responsibilities of a Project Manager According to PMBOK.The role of a project manager is crucial in ensuring the successful delivery of any project. They are responsible for leading and guiding the team, managing resources, and overseeing the entire project lifecycle from inception to completion. The Project Management Body of Knowledge (PMBOK) provides a comprehensive framework for project management, outlining the key responsibilities and skills required for project managers to succeed.1. Project Planning:A project manager's journey begins with planning. They need to develop a detailed project plan that outlines the scope, timeline, budget, and resources required for the project. This plan serves as a roadmap for the entire team, guiding them through the various stages of the project. Theproject manager is responsible for ensuring that all stakeholders are aligned with the plan and understand their roles and responsibilities.2. Stakeholder Management:Project managers must effectively manage stakeholders, which includes understanding their needs, expectations, and concerns. They need to communicate regularly with stakeholders, keeping them informed about the project's progress and addressing any issues or concerns that arise. Stakeholder management is crucial for maintaining buy-in and support throughout the project lifecycle.3. Team Leadership:The project manager is responsible for leading and motivating the project team. They need to delegate tasks, monitor progress, and provide feedback to ensure that the team is working efficiently and effectively. The project manager must also foster a positive team culture that encourages collaboration, innovation, and continuousimprovement.4. Risk Management:Identifying, analyzing, and responding to project risks is a crucial responsibility of the project manager. They need to develop a risk management plan that outlines strategies for mitigating, monitoring, and responding to risks that could potentially impact the project's success. The project manager must also have the ability to make quick decisions in response to unexpected risks that arise during the project lifecycle.5. Scope Management:Ensuring that the project remains within the defined scope is a fundamental responsibility of the project manager. They need to closely monitor the scope and ensure that any changes are properly evaluated, approved, and communicated to the team and stakeholders. Scope creep can quickly lead to budget overruns and timeline delays, soit's crucial for the project manager to maintain a strictscope management process.6. Time Management:Time is money, and project managers understand this better than anyone. They are responsible for ensuring that the project stays on track and meets its deadlines. This involves creating a realistic timeline, monitoring progress, and taking corrective actions when necessary. The project manager must also have the ability to prioritize tasks and adjust the plan as needed to ensure that the project is completed on time.7. Cost Management:Managing the project budget is another keyresponsibility of the project manager. They need to develop a budget plan, track expenses, and ensure that the project remains within the allocated budget. Cost overruns can quickly erode project profits, so it's crucial for the project manager to have a strong understanding of financial management and cost control techniques.8. Quality Management:Delivering a high-quality project is the ultimate goalof any project manager. They are responsible for ensuring that the project meets the defined quality standards and expectations. This involves developing a quality management plan, conducting quality assurance activities, and leading quality improvement initiatives. The project manager must also have the ability to identify and correct qualityissues to ensure that the final deliverable meets the customer's requirements.9. Communication Management:Effective communication is essential for project success. The project manager is responsible for developinga communication plan that outlines how information will be shared within the team and with stakeholders. They need to ensure that regular updates are provided, and that all stakeholders are kept informed about the project's progress, challenges, and successes. The project manager must alsohave the ability to communicate clearly and effectively in both written and verbal formats.10. Closure Management:Although the project may be nearing its end, theproject manager's responsibilities do not end there. They are responsible for ensuring that the project is properly closed out, including documenting lessons learned, conducting a post-project review, and disbursing any remaining funds. Closure management is crucial for ensuring that the project team can move on to the next project with a clear understanding of what worked well and what could be improved upon in future projects.In conclusion, the role of a project manager is diverse and demanding, requiring a strong understanding of project management principles, excellent leadership skills, and the ability to adapt to changing project environments. By effectively managing the project lifecycle, leading the team, and communicating effectively with stakeholders, project managers can ensure that projects are delivered ontime, within budget, and meeting the expectations of all involved.。
PMP备考知识的细节支持(第2版)®©整理:guojiayoung(项目管理者联盟/的ID)附注二十五大模拟试题200道-得分×0.8>137分通过PMP考试希望很大bayou级别:论坛游民积分:15经验:45文章:15注册:04-05-27 14:32发表: 2004-06-01 09:43:46 人气:1321. The purpose of project plan development is to—项目计划规划的目的是 [ ]a. Create a document to guide project execution and control制定项目文件,指导项目执行和控制b. Document project assumptions and constraints提出项目的假设和约束条件c. Promote communication among stakeholders促进项目干系人之间的沟通d. Define key project reports确定主要项目报告Please refer to the following information to answer questions 2.请参阅以下信息,回答问题2。
You have been assigned as the project manager on a project with a clearly defined scope limited to the design-and-build phase of a product assembly line. A member of the client’s team has asked a functional supervisor on the project to complete a small job during the installation phase of the project. The functional supervisor referred the client to the project manager.您已经被委派为某项目的项目经理,职权范围明确界定,限于产品总装的设计及建设阶段。
项目管理49个过程组项目管理中有49个过程组,分为5个过程组群和10个知识领域。
以下是这些过程组的列表:1. 启动过程组(Initiating Process Group):- 制定项目章程(Develop Project Charter)- 确定干系人(Identify Stakeholders)2. 计划过程组(Planning Process Group):- 制定项目管理计划(Develop Project Management Plan)- 管理干系人(Manage Stakeholder Engagement)- 制定范围计划(Plan Scope Management)- 收集需求(Collect Requirements)- 定义范围(Define Scope)- 制定工作分解结构(Create Work Breakdown Structure)- 制定进度计划(Develop Schedule)- 制定成本计划(Develop Cost Plan)- 制定质量计划(Develop Quality Plan)- 制定资源计划(Develop Resource Plan)- 制定沟通计划(Develop Communication Plan)- 制定风险管理计划(Develop Risk Management Plan)- 制定采购计划(Develop Procurement Plan)- 制定相关方参与计划(Develop Stakeholder Participation Plan)3. 执行过程组(Executing Process Group):- 指导和管理项目工作(Direct and Manage Project Work) - 实施质量保证(Implement Quality Assurance)- 获取资源(Acquire Resources)- 建设团队(Build Team)- 管理团队(Manage Team)- 分发信息(Distribute Information)- 管理相关方参与(Manage Stakeholder Participation)- 实施风险应对(Implement Risk Responses)- 实施采购(Implement Procurements)4. 监控过程组(Monitoring and Controlling Process Group): - 监控项目工作(Monitor Project Work)- 监控项目范围(Monitor Project Scope)- 验收项目交付物(Validate Project Deliverables)- 控制范围(Control Scope)- 控制进度(Control Schedule)- 控制成本(Control Cost)- 控制质量(Control Quality)- 控制资源(Control Resources)- 监控沟通(Monitor Communication)- 监控风险(Monitor Risks)- 管理采购(Manage Procurements)5. 收尾过程组(Closing Process Group):- 结束项目或阶段(Close Project or Phase)- 确认干系人的满意度(Validate Stakeholder Satisfaction)- 归档项目或阶段信息(Archive Project or Phase Information) - 更新组织过程资产(Update Organizational Process Assets) - 更新项目文件(Update Project Documents)。
Scope Planning:Outputs范围规划:成果Project Scope Management Plan项目范围管理计划The project scope management plan provides guidance on how project scope will bedefined,documented,verified,managed,and controlled by the project management team.The components of a project scope management plan include:项目范围管理计划是项目管理团队确定、记载、核实、管理和控制项目范围的指南。
项目范围管理计划的内容有:A process to prepare a detailed project scope statement based upon the preliminary project scope statement根据项目初步范围说明书编制详细项目范围说明书的一个过程A process that enables the creation of the WBS from the detailed project scope statement,and establishes how the WBS will be maintained and approved能够根据详细的项目范围说明书制作工作分解结构,并确定如何维持与批准该工作分解结构的一个过程A process that specifies how formal verification and acceptance of the completed project deliverables will be obtained规定如何正式核实与验收项目已完成可交付成果的一个过程A process to control how requests for changes to the detailed project scope statement will be processed.This process is directly linked to the integrated change control process.控制详细项目范围说明书变更请求处理方式的一个过程。
Tips for Effective Project ScopeManagement项目范围管理的有效技巧在项目管理中,范围管理是确保项目能够按时、按预算、按要求完成的关键因素之一。
范围管理涉及到定义项目的目标和可交付成果,确定项目的边界和限制,并确保项目团队在整个项目周期内能够控制和管理范围的变化。
本文将介绍一些有效的项目范围管理技巧,帮助项目经理和团队实现项目目标。
1. 明确项目目标和可交付成果在项目启动阶段,项目经理和团队应该与相关利益相关者明确项目的目标和可交付成果。
这意味着要确保每个人对项目的期望和目标有清晰的理解。
通过与利益相关者沟通和协商,确定项目的范围,并将其记录在项目范围说明书中。
这样可以为项目提供一个明确的基础,避免后续范围变更和冲突。
2. 制定详细的工作分解结构(WBS)工作分解结构是将项目范围分解为可管理的任务和活动的一种方法。
通过将项目分解为更小的组成部分,可以更好地理解项目的复杂性,并更容易进行资源分配和进度控制。
制定详细的WBS可以帮助项目团队更好地规划和执行项目,确保项目按时、按预算完成。
3. 有效地进行需求管理需求管理是项目范围管理的重要组成部分。
项目团队应该与利益相关者合作,确保所有需求都被明确记录,并对其进行优先级排序。
通过建立一个有效的需求管理过程,可以帮助项目团队更好地理解和满足利益相关者的期望,减少范围变更和冲突的可能性。
4. 管理范围变更在项目执行过程中,范围变更是不可避免的。
项目经理和团队应该建立一个范围变更管理过程,以确保每个变更都经过评估、批准和控制。
范围变更管理可以帮助项目团队更好地控制范围的变化,避免项目范围的蔓延和项目目标的偏离。
5. 使用适当的工具和技术在项目范围管理中,使用适当的工具和技术可以提高工作效率和质量。
例如,项目团队可以使用工作分解结构软件来创建和管理WBS,使用需求管理工具来跟踪和管理需求,使用项目管理软件来跟踪和控制项目进度和资源。
确定项目管理范围的意义
范围管理(Scope Management)是项目管理的一个专用词汇,它的首要任务是界定项目包含且只包含所有需要完成的工作,并对其它项目管理工作起指导作用,以保证顺利完成项目所需要的所有过程。
通常来说确定了项目范围的同时也就定义了项目的工作边界,明确了项目的目标和项目主要的可交付成果。
对于无论是新技术或是新产品的研发项目,或者是服务性的项目,如果不能有效地定义并控制项目的范围,将会带来许多严重问题的产生,如:项目实际要求的、但没有明确定义的工作将不能得到有效执行,或者项目的范围盲目扩大,进而影响项目的预算。
例如:迫于客户压力,不得不做一些份外工作,或自身缺乏明确的管理观念时,都将导致这样的结果。
因此,由上可以看出确定项目的范围对项目管理来说可以产生如下作用:
(1)提高费用、时间和资源估算的准确性。
项目的工作边界如果被定义清楚,则就具体明确了项目的实际工作内容,同时也就为项目实施过程中所需要花费的费用、时间、资源的估计打下了一定的基础。
(2)确定了进度测量和控制的基准。
项目范围是项目计划的基础,如果项目范围确定了就为项目进度计划和控制确定了基准。
(3)有助于清楚地分派责任。
在项目范围确定的同时,也就确定了项目的具体工作任务,所以为进一步分派任务打下了基础。
如何判断项目在范围管理方面是否合理呢?我们可以通过回答以下问题来对管理的合理性进行判断:
(1)项目是否拥有支持项目启动的正式文本(如合同书、授权书或其它的项目相关文件)?
(2)是否有正规的项目说明文档?
(3)是否定义了工作分解结构WBS?是否有正式的项目范围变更程序?。
范围管理定义范围管理(Scope Management)是项目管理的一个关键过程,它涉及识别、定义和控制项目中的工作范围。
范围管理是确保项目在规定的时间、成本和质量约束下实现目标的重要手段。
本文将详细介绍范围管理的定义、目标和步骤。
一、范围管理的定义范围管理是指在项目管理过程中,通过明确规定项目的目标和范围,确保项目按照既定要求进行,并在项目执行过程中进行范围变更控制,以保证项目顺利完成的一系列活动。
范围管理包括以下几个方面:1. 识别项目范围:确定项目的目标和范围,明确项目的界限。
2. 定义项目范围:详细描述项目的工作内容和可交付成果,制定项目工作的具体计划。
3. 创建工作分解结构(WBS):将项目范围分解为更小的、具体的工作包和任务,以便于分配、跟踪和控制。
4. 确定控制范围:在项目执行阶段,及时发现并记录项目范围的变更,并根据情况进行相应的变更控制。
5. 验收项目交付成果:在项目完成时,对项目交付的成果进行验收,确保其符合既定的要求。
二、范围管理的目标范围管理的目标是确保项目按照既定的范围进行,并实现项目的目标。
范围管理的主要目标包括:1. 确定项目的范围和目标:通过识别和定义项目的范围,明确项目的目标和需求,为项目的后续工作提供明确的指导。
2. 提高项目规划的准确性:通过详细描述项目的工作内容和可交付成果,制定具体的项目计划,以提高项目规划的准确性。
3. 控制项目范围:在项目执行过程中,及时发现和记录项目范围的变更,并根据情况进行相应的变更控制,以确保项目按照既定的要求进行。
4. 优化项目资源的利用:通过工作分解结构(WBS)的创建,将项目范围分解为更小的、具体的工作包和任务,以便于项目资源的分配、跟踪和控制,提高项目资源的利用效率。
5. 确保项目交付成果的质量:在项目完成时,对项目交付的成果进行验收,确保其符合既定的要求,提高项目交付成果的质量。
三、范围管理的步骤范围管理的具体步骤包括以下几个方面:1. 识别项目范围:明确项目的目标和需求,了解项目的背景和相关信息,识别项目的关键要素和范围,为后续工作的定义提供基础。
软考高级十大知识领域常用单词汇总一、项目整合管理(Project Integration Management)1. Initiating [ɪˈnɪʃieɪtɪŋ] (v. - 动名词形式) - 启动。
2. Planning [ˈplænɪŋ] (n. - 名词) - 规划。
3. Executing [ˈeksɪkjuːtɪŋ] (v. - 动名词形式) - 执行。
4. Monitoring [ˈmɒnɪtərɪŋ] (v. - 动名词形式) - 监控。
5. Controlling [kənˈtrəʊlɪŋ] (v. - 动名词形式) - 控制。
6. Closing [ˈkləʊzɪŋ] (v. - 动名词形式) - 收尾。
7. Integrated [ˈɪntɪɡreɪtɪd] (adj. - 形容词) - 整合的,综合的。
8. Project Charter [ˈprɒdʒekt ˈtʃɑːtə(r)] (n. - 名词短语) - 项目章程。
二、项目范围管理(Project Scope Management)1. Scope [skəʊp] (n. - 名词) - 范围。
2. Scope Statement [skəʊp ˈsteɪtmənt] (n. - 名词短语) - 范围说明书。
3. Work Breakdown Structure [wɜːk ˈbreɪkdaʊn ˈstrʌktʃə(r)] (n. - 名词短语) (WBS) - 工作分解结构。
4. Scope Verification [skəʊp ˌverɪfɪˈkeɪʃn] (n. - 名词短语) - 范围核实。
5. Scope Creep [skəʊp kriːp] (n. - 名词短语) - 范围蔓延。
三、项目时间管理(Project Time Management)1. Activity [ækˈtɪvəti] (n. - 名词) - 活动。
信息系统项目管理高级英语单词一、项目管理基础。
1. Project [ˈprɒdʒekt] (n.) - 项目。
2. Management [ˈmænɪdʒmənt] (n.) - 管理。
3. Stakeholder [ˈsteɪkhəʊldə(r)] (n.) - 干系人。
4. Scope [skəʊp] (n.) - 范围。
5. Schedule [ˈʃedju:l] (n.) - 进度计划;(v.)安排。
6. Cost [kɒst] (n.) - 成本;(v.)花费。
7. Quality [ˈkwɒləti] (n.) - 质量。
8. Resource [rɪˈsɔ:s] (n.) - 资源。
9. Risk [rɪsk] (n.) - 风险;(v.)冒……风险。
10. Communication [kəˌmju:nɪˈkeɪʃn] (n.) - 沟通。
二、项目管理过程组。
1. Initiating [ɪˈnɪʃieɪtɪŋ] (n.) - 启动过程组。
2. Planning [ˈplænɪŋ] (n.) - 规划过程组。
3. Executing [ɪgˈzekjʊtɪŋ] (n.) - 执行过程组。
4. Monitoring [ˈmɒnɪtərɪŋ] (n.) - 监控过程组。
5. Closing [ˈkləʊzɪŋ] (n.) - 收尾过程组。
三、项目管理知识领域相关。
1. Integration [ˌɪntɪˈɡreɪʃn] (n.) - 整合管理。
2. Scope Management - 范围管理。
- Define Scope [dɪˈfaɪn skəʊp] - 定义范围。
- Verify Scope [ˈverɪfaɪ skəʊp] - 核实范围。
- Control Scope [kənˈtrəʊl skəʊp] - 控制范围。
3. Schedule Management - 进度管理。
单选题(每题1分,共200道题)1、[单选] 在项目开始时,一名关键资源计划退休。
项目经理应该怎么做?At the start of a project, a key resource plans to retire. What the project manager should do?A:修订工作分解结构(WBS)Revise the work breakdown structure (WBS).B:与项目发起人合作,找到适合的替代资源Work with the sponsor to find a suitable replacement for the key resource.C:与职能经理协商获得一名同等相当资源Negotiate with the functional manager to obtain to obtain an equal resource.D:更新风险登记册Update the risk register.正确答案:D 你的答案:D解析:11.6.3.2 实施风险应对:输出:项目文件更新。
一名关键资源计划退休是新识别的风险,应首先更新风险登记册。
2、[单选] 在项目执行阶段,项目经理意识到项目相关方一直延迟答复敏感性电子邮件。
项目经理应该怎么做?During a project’s execution phase, the project manager realizes that a stakeholder is consistently late in responding to sensitive emails. What should the project manager do?A:将其作为一个沟通问题记录在风险登记册中。
Log it in the risk register as a communication issue.B:参阅监督沟通过程,获得替代沟通方式。
S c o p e-M a n a g e m e n t-P l a n-CAL-FENGHAI-(2020YEAR-YICAI)_JINGBIANS COPE M ANAGEMENT P LAN T EMPLATEThis Project Scope Management Plan Template is free for you to copyand use on your project and within your organization. We hope that you findthistemplate useful and welcome your comments. Public distribution of thisdocumentis only permitted from the Project Management Docs official website at:M ANAGEMENT P LAN<P ROJECT N AME>C OMPANY N AMES TREET A DDRESSC ITY,S TATE Z IP C ODED ATET ABLE OF C ONTENTSI NTRODUCTION................................................... 错误!未定义书签。
S COPE M ANAGEMENT A PPROACH........................................ 错误!未定义书签。
R OLES AND R ESPONSIBILITIES........................................ 错误!未定义书签。
S COPE D EFINITION ............................................... 错误!未定义书签。
S COPE M ANAGEMENT P LAN T EMPLATEThis Project Scope Management Plan Template is free for you to copyand use on your project and within your organization. We hope that you find this template useful and welcome your comments. Public distribution of this document is only permitted from the Project Management Docs official website at:www.P roject M anagement D S COPE M ANAGEMENT P LAN<P ROJECT N AME>C OMPANY N AMES TREET A DDRESSC ITY,S TATE Z IP C ODED ATET ABLE OF C ONTENTSI NTRODUCTION (3)S COPE M ANAGEMENT A PPROACH (4)R OLES AND R ESPONSIBILITIES (4)S COPE D EFINITION (5)P ROJECT S COPE S TATEMENT (6)W ORK B REAKDOWN S TRUCTURE (7)S COPE V ERIFICATION (8)S COPE C ONTROL (8)S PONSOR A CCEPTANCE (10)I NTRODUCTIONScope Management is the collection of processes which ensure that the project includes all the work required to complete it while excluding all work which is not necessary to complete it. The Scope Management Plan details how the project scope will be defined, developed, and verified. It clearly defines who is responsible for managing the projects’ scope and acts as a guide for managing and controlling the scope.Project Scope Management follows a five step process; Collect Requirements, Define Scope, Create WBS, Verify Scope, and Control Scope.1)Collect Requirements – this first step is the process by which we define and document therequirements needed to meet all project objectives. The foundation of this process is the project charter and stakeholder register. From these, the team can identify requirements, collectively discuss details associated with meeting each requirement, conduct interviews and follow-on discussion to clarify the requirements, and document the requirements insufficient detail to measure them once the project begins the execution phase. Thisdocumentation also serves as an input to the next step in the process which is to definescope.2)Define Scope – this step is critical to project success as it requires the development of adetailed project/product description to include deliverables, assumptions, and constraints and establishes the framework within which project work must be performed.3)Create WBS – this process breaks project deliverables down into progressively smallerand more manageable components which, at the lowest level, are called work packages.This hierarchical structure allows for more simplicity in scheduling, costing, monitoring, and controlling the project.4)Verify Scope – this is the process by which the project team receives a formalizedacceptance of all deliverables with the sponsor and/or customer.5)Control Scope – this is the process of monitoring/controlling the project/product scope aswell as managing any changes in the scope baseline. Changes may be necessary to theproject scope but it is imperative they are controlled and integrated in order to preventscope creep.The Scope Management Plan provides the scope framework for this project. This plan documents the scope management approach; roles and responsibilities as they pertain to project scope; scope definition; verification and control measures; scope change control; and the project’s work breakdown structure. Any project communication which pertains to the project’s scope should adhere to the Scope Management Plan.This project is for designing, programming, and testing a new software product which will be used to track the company’s finances and improve various financial processes. This includes design of the software, all programming and coding, and testing/validation of the software. No external resources or outsourcing are anticipated for this project.S COPE M ANAGEMENT A PPROACHIt is important that the approach to managing the project s’ scope be clearly defined and documented in detail. This section provides a summary of the Scope Management Plan in which it addresses the following:•Who has authority and responsibility for scope management•How the scope is defined (i.e. Scope Statement, WBS, WBS Dictionary, Statement of Work, etc.)•How the scope is measured and verified (i.e. Quality Checklists, Scope Baseline, Work Performance Measurements, etc.)•The scope change process (who initiates, who authorizes, etc.)•Who is responsible for accepting the final project deliverable and approves acceptance of project scopeFor this project, scope management will be the sole responsibility of the Project Manager. The scope for this project is defined by the Scope Statement, Work Breakdown Structure (WBS) and WBS Dictionary. The Project Manager, Sponsor and Stakeholders will establish and approve documentation for measuring project scope which includes deliverable quality checklists and work performance measurements. Proposed scope changes may be initiated by the Project Manager, Stakeholders or any member of the project team. All change requests will be submitted to the Project Manager who will then evaluate the requested scope change. Upon acceptance of the scope change request the Project Manager will submit the scope change request to the Change Control Board and Project Sponsor for acceptance. Upon approval of scope changes by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all stakeholders. Based on feedback and input from the Project Manager and Stakeholders, the Project Sponsor is responsible for the acceptance of the final project deliverables and project scope.R OLES AND R ESPONSIBILITIESIn order to successfully manage a projects’scope it’s important that all roles and responsibilit ies for scope management are clearly defined. This section defines the role of the Project Manager, Project Team, Stakeholders and other key persons who are involved in managing the scope of the project. It should state who is responsible for scope management and who is responsible for accepting the deliverables of the project as defined by the projects’ scope. Any other roles in scope management should also be stated in this section.The Project Manager, Sponsor and team will all play key roles in managing the scope of this project. As such, the project sponsor, manager, and team members must be aware of their responsibilities in order to ensure that work performed on the project is within the established scope throughout the entire duration of the project. The table below defines the roles and responsibilities for the scope management of this project.Name Role ResponsibilitiesJohn Doe Sponsor -Approve or deny scope change requests asappropriate-Evaluate need for scope change requests-Accept project deliverablesJane Doe Project Manager -Measure and verify project scope-Facilitate scope change requests-Facilitate impact assessments of scopechange requests-Organize and facilitate scheduled changecontrol meetings-Communicate outcomes of scope changerequests-Update project documents upon approval ofall scope changesBob Jones Team Lead -Measure and verify project scope-Validate scope change requests-Participate in impact assessments of scopechange requests-Communicate outcomes of scope changerequests to team-Facilitate team level change review process John Smith Team Member -Participate in defining change resolutions-Evaluate the need for scope changes andcommunicate them to the project manager asnecessaryTom Brown Team Member -Participate in defining change resolutions-Evaluate the need for scope changes andcommunicate them to the project manager asnecessaryTable 1.1, Scope Management Roles and ResponsibilitiesS COPE D EFINITIONThe scope definition section details the process of developing a detailed description of the project and its deliverables. This can only be completed after the requirements have been identified and defined during the requirements definition process. During the requirements definition process three documents were created; Requirements Documentation, Requirements Management Plan and a Requirements Traceability Matrix. You can refer to these documents when defining the projects’ scope.This section should explain the process you followed to develop the detailed description of the project and its deliverables. If you used other documents such as the Project Charter, Preliminary Project Scope Statement or Requirements Documentation you should identify them and all other documents used. You should tie the scope definition process back to the requirements definition as the projects’ scope answers the requirements for the project.You should also document the tools and techniques used to define the project scope such as expert judgment, product analysis, alternatives identification or facilitated workshops.The scope for this project was defined through a comprehensive requirements collection process. First, a thorough analysis was performed on the company’s current software applications based on employee and user feedback. From this information, the project team developed the project requirements documentation, the requirements management plan, and the requirements traceability matrix for what the new software application must accomplish.The project description and deliverables were developed based on the requirements collection process and input from subject matter experts in software design, technical support, programming and business applications. This process of expert judgment provided feedback on the most effective ways to meet the original requirements of providing a new software platform from which the company can improve its financial tracking and internal financial processes.P ROJECT S COPE S TATEMENTThe project scope statement details the project’s delive rables and the work necessary to create these deliverables. The Project Scope Statement should contain the following components: •Product Scope Description – describes what the project will accomplish•Product Acceptance Criteria – describes what requirements must be met in order for the project to be accepted as complete•Project Deliverables – detailed list of deliverables the project will result in•Project Exclusions – description of work that is not included in the project and outside of the scope•Project Constraints – lists limits on resources for time, money, manpower, or equipment (capital)•Project Assumptions – describes the list of assumptions the project team and stakeholders are working under to complete the projectThe project scope statement provides a detailed description of the project, deliverables, constraints, exclusions, assumptions, and acceptance criteria. Additionally, the scope statement includes what work should not be performed in order to eliminate any implied but unnecessary work which falls outside the of the project’s scope.This project includes the design, programming, and testing of a new software application for tracking the company’s finances. The deliverables for this project are a completed software application for finance tracking with the flexibility to modify and expand the application as necessary in the future. This project will be accepted once the new software has been successfully tested in each department and has been shown to be compatible with the company’s current information technology (IT) infrastructure. This project does not include ongoing operations and maintenance of the software. Only internal personnel and resources may be used for this project. Additionally, the project is not to exceed 180 days in duration or $450,000 in spending. Assumptions for this project are that support will be provided by the project sponsorand all department managers and that adequate internal resources are available for the successful completion of this project.W ORK B REAKDOWN S TRUCTUREThe Work Breakdown Structure (WBS) and Work Breakdown Structure Dictionary are keyelements to effective scope management. This section should discuss how the project scope is to be subdivided into smaller deliverables in the WBS and WBS Dictionary and how these smaller components are managed during the life of the project.In order to effectively manage the work required to complete this project, it will be subdivided into individual work packages which will not exceed 40 hours of work. This will allow theProject M anager to more effectively manage the project’s scope as the project team works on the tasks necessary for project completion. The project is broken down into three phases: the design phase; the programming phase; and the testing phase. Each of these phases is then subdivided further down to work packages which will require no more than 40 hours of work and no less than 4 hours of work (see WBS structure below).Figure 1.1, Work Breakdown Structure (WBS)In order to more clearly define the work necessary for project completion the WBS Dictionary is used. The WBS Dictionary includes an entry for each WBS element. The WBS Dictionary includes a detailed description of work for each element and the deliverables, budget andresource needs for that element. The project team will use the WBS Dictionary as a statement of work for each WBS element.New Software Project 1.3 Testing Phase 1.2 Programming Phase 1.1 Design Phase 1.1.1 First Design Phase1.1.2 Second Design Phase 1.1.1.2 Design Task #2 1.1.1.1 Design Task #1 1.1.2.1 Design Task #3 1.1.2.2 Design Task #4 1.2.1 Programming Task #1 1.2.2 Programming Task #2 1.3.3 Testing Task #3 1.3.2 Testing Task #2 1.3.1 Testing Task #1Level WBSElement Name Description of Work Deliverables Budget Resources CodeTable 1.2, WBS DictionaryS COPE V ERIFICATIONScope verification discusses how the deliverables will be verified against the original scope and how the deliverables from the project will be formally accepted. The deliverables for the project should be formally accepted and signed off on by the customer throughout the lifecycle of the project and not held back as a single deliverable at the end of the project.As this project progresses the Project Manager will verify interim project deliverables against the original scope as defined in the scope statement, WBS and WBS Dictionary. Once the Project Manager verifies that the scope meets the requirements defined in the project plan, the Project Manager and Sponsor will meet for formal acceptance of the deliverable. During this meeting the Project Manager will present the deliverable to the Project Sponsor for formal acceptance. The Project Sponsor will accept the deliverable by signing a project deliverable acceptance document. This will ensure that project work remains within the scope of the project on a consistent basis throughout the life of the project.S COPE C ONTROLScope control is the process of monitoring the status of the scope of the project. This section also details the change process for making changes to the scope baseline.The Project Manager and the project team will work together to control of the scope of the project. The project team will leverage the WBS Dictionary by using it as a statement of work for each WBS element. The project team will ensure that they perform only the work described in the WBS dictionary and generate the defined deliverables for each WBS element. The Project Manager will oversee the project team and the progression of the project to ensure that this scope control process if followed.If a change to the project scope is needed the process for recommending changes to the scope of the project must be carried out. Any project team member or sponsor can request changes to the project scope. All change requests must be submitted to the Project Manager in the form of a project change request document. The Project Manager will then review the suggested change to the scope of the project. The Project Manager will then either deny the change request if it does not apply to the intent of the project or convene a change control meeting between the project team and Sponsor to review the change request further and perform an impact assessment of the change. If the change request receives initial approval by the Project Manager and Sponsor, the Project Manager will then formally submit the change request to the Change Control Board. Ifthe Change Control Board approves the scope change the Project Sponsor will then formally accept the change by signing the project change control document. Upon acceptance of the scope change by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all project team members stakeholders.S PONSOR A CCEPTANCEApproved by the Project Sponsor:__________________________________________ Date: ___________________ <Project Sponsor><Project Sponsor Title>This free Project Scope Management Plan Template is brought to you by 。