What is Project Scope Management n n Scope








- Slides: 8
What is Project Scope Management? n n Scope refers to all the work involved in creating the products of the project and the processes used to create them. Project scope management n n Including the processes involved in defining and controlling what is or is not included in a project Ensuring that the project team and stakeholders have the same understanding of what products the project will produce and what processes the project team will use to produce them
What is Project Scope Management? There are five main processes involved in project scope management: n n n Initiation: committing the organization to begin a project or continue to the next phase of a project Scope planning: developing documents to provide the basis for future project decisions, including the criteria for determining if a project or phase has been completed successfully Scope definition: subdividing the major project deliverables into smaller, more manageable components Scope verification: formalizing acceptance of the project scope Scope change control: controlling changes to project scope
Initiation Process n The project initiation process involves: n n Identifying potential projects Using realistic methods to select which projects to work on Formalizing their initiation by issuing some sort of project charter A project charter is a document that formally recognizes the existence of a project and provides direction on the project’s objectives and management.
Scope Planning Process n n n Involves developing documents to provide the basis for future project decisions, including the criteria for determining if a project or phase has been completed successfully Inputs: the project charter, descriptions of the products involved in the project, project constraints, and project assumptions Output: the creation of a written scope statement, including supporting detail, and a project scope management plan
Scope Planning Process (Cont. ) n n A scope statement is a document used to develop and confirm a common understanding of the project scope. The scope statement should include: n n n A project justification A brief description of the project’s products A summary of all project deliverables A statement of what determines project success References to supporting documents
Scope Definition Process n n The scope definition process is the process of breaking work into manageable pieces. Good scope definition is very important to project success because: n n it helps improve the accuracy of time, cost, and resource estimates, it defines a baseline for performance measurement and project control, and it aids in communicating clear work responsibilities Output: Work Breakdown Structure (WBS) for the project
Work Breakdown Structure (WBS) n n n The project management team has to carefully establish the project’s objectives, then break the project down into manageable parts by using the “work breakdown structure (WBS)”. The WBS defines the project by dividing it into its major subcomponents (or tasks), which are then subdivided into more detailed components, and finally into a set of activities and their related costs. The WBS for Microsoft’s operating system – Windows XP Level 1 2 2 3 3 3 4 Level ID Number 1. 0 1. 1 1. 21 1. 22 1. 231 Activity Develop/launch Windows XP Operating System Development of graphic user interfaces (GUIs) Ensure compatibility with earlier Windows versions Compatibility with Windows 98 Compatibility with Windows NT Compatibility with Windows 2000 Ability to import files
Scope Verification & Change Control Processes n n n The scope verification process involves formal acceptance of the project scope by the stakeholders. This acceptance is often achieved by a customer signoff on key deliverables and the entire project. To receive formal acceptance of the project scope, the project team must develop clear documentation of the project’s products and procedures to evaluate if they were completed correctly and satisfactorily. The scope change control process involves controlling changes to the project scope. In order to minimize scope change control, it is crucial to do a good job of verifying project scope.