Oversees the scope change management process. Approves scope change requests within his/her authority. Escalates scope and change issues. Ensures that scope changes are incorporated into appropriate project documents [Name] Contract Manager May have a role in deliverable verification and acceptance when the deliverable is required under contract terms. [Name] Project Team Members Help develop the project scope statement. and Subject Matter Submit scope change requests. Experts (SMEs) Review Scope Change requests when assigned. Provide feedback as and when required. Participate in team-level scope change reviews. [Name] Independent Provides an ongoing independent review and Verification and analysis of project scope management Validation (IV&V) practices. Monitors scope changes and provide feedback. Scope Management Processes Definition of Scope [In this section, describe the approach to developing the project scope statement.] Example: This process takes the high-level product descriptions, assumptions and constraints, as documented in the Project Charter, and uses them to create a more detailed scope in the Project Scope Statement. The result of the process is a detailed definition of the product and/or service the project will produce. This section details the process of developing a detailed description of the project and its deliverables. The Scope Statement details the project’s deliverables and work necessary to create these deliverables. The project Scope Statement can contain, but is not limited to, the following components: Executive Summary Brief summary of the project – Business Objectives Should be stated in business terms – Product Scope Description Describes what the project will accomplish – Project Deliverables A detailed list of deliverables the project will produce – Product Acceptance Criteria Describes what requirements must be met for the project to be – accepted as complete
Oversees the scope change management process. Approves scope change requests within his/her authority. Escalates scope and change issues. Ensures that scope changes are incorporated into appropriate project documents [Name] Contract Manager May have a role in deliverable verification and acceptance when the deliverable is required under contract terms. [Name] Project Team Members and Subject Matter Experts (SMEs) Help develop the project scope statement. Submit scope change requests. Review Scope Change requests when assigned. Provide feedback as and when required. Participate in team-level scope change reviews. [Name] Independent Verification and Validation (IV&V) Provides an ongoing independent review and analysis of project scope management practices. Monitors scope changes and provide feedback. Scope Management Processes Definition of Scope [In this section, describe the approach to developing the project scope statement.] Example: This process takes the high-level product descriptions, assumptions and constraints, as documented in the Project Charter, and uses them to create a more detailed scope in the Project Scope Statement. The result of the process is a detailed definition of the product and/or service the project will produce. This section details the process of developing a detailed description of the project and its deliverables. The Scope Statement details the project’s deliverables and work necessary to create these deliverables. The project Scope Statement can contain, but is not limited to, the following components: Executive Summary – Brief summary of the project Business Objectives – Should be stated in business terms Product Scope Description – Describes what the project will accomplish Project Deliverables – A detailed list of deliverables the project will produce Product Acceptance Criteria – Describes what requirements must be met for the project to be accepted as complete
Scope_Management_Plan_Template_with_Instructions.docx