Project Scope Management - Definition, Processes, Templates
You find the definition and the processes involved in Project Scope Management (PMBOK®) and free downloadable templates further down on this page.
Definition of Scope Management (PMI™)
Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project. (PMBOK® Guide)
Project scope is the work that needs to be accomplished to deliver a product, service, or result with the specified features and functions.
Product scope are the features and functions that characterize a product, service, or result.
Scope Management Processes (PMI™)
Plan Project Scope Management
- Plan scope management is the process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled.
- Collect requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
- Define scope is the process of developing a detailed description of the project and product.
- Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.
- Validate scope is the process of formalizing acceptance of the completed project deliverables.
- Control scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Download Area Project Scope Management Templates
All you need to know about Project Scope Management
Incomplete or missed requirements, omissions, ambiguous product features, lack of user involvement, unrealistic customer expectations, and the proverbial scope creep can result in cost overruns, missed deadlines, poor product quality, and can very well ruin a project. Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects describes how to elicit, document, and manage requirements to control project scope creep. It also explains how to manage project stakeholders to minimize the risk of an ever-growing list of user requirements.
The book begins by discussing how to collect project requirements and define the project scope. Next, it considers the creation of WBS and examines the verification and control of the scope. Most of the book is dedicated to explaining how to collect requirements and how to define product and project scope in as much as they represent the bulk of the project scope management work undertaken on any project regardless of the industry or the nature of the work involved.
The book maintains a focus on practical and sensible tools and techniques rather than academic theories. It examines five different projects and traces their development from a project scope management perspective from project initiation to the end of the execution and control phases. The types of projects considered include CRM system implementation, mobile number portability, port upgrade, energy-efficient house design, and airport check-in kiosk software.
After reading this book, you will learn how to create project charters, high-level scope, detailed requirements specifications, requirements management plans, traceability matrices, and a work breakdown structure for the projects covered.
Project Scope Management Overview
What are Project Scope and Product Scope?
Scope management defines the extent of required works and results and then ensures that this works and results - and only this works and results – are delivered. Work and results are divided into project scope and product scope. Product scope refers to the detailed result and its functions. Project scope, on the other hand, rather explains the process of how the result should be achieved.
What is the Scope Management Plan?
The scope management plan includes the detailed scope definition. The scope is broken down in manageable packages, and detailed explanations how the scope is realized, and how it is controlled, are included. The scope management plan is a part of the project management plan, which is prepared by the project manager and the management team during the planning phase. The plan is approved by the project sponsor before the project is realized. It may be updated during the project life cycle if needed.
Collecting Requirements and Defining Scope
In order to define the scope, requirements from all entitled stakeholders must be collected, recorded and categorized. It may well happen that certain requirements overlap or even contradict each other. It is therefore of the utmost importance to clarify such discrepancies in advance. Nothing may be added, omitted or changed without the consent of the project sponsor.
How to Deal with Changes?
The need or desire for change may arise in the course of the ongoing project for a variety of reasons. The detailed approach how to deal with such and any other changes is described in the change management procedure and proceeded accordingly. The change management procedure is described either in the project management plan directly or in a change management plan that is part of the project management plan.
Scope Control and Verification
Within the framework of the quality management during the project execution, it is closely monitored and controlled that the work results correspond to the specifications and requirements. At different times various tests of parts of the result and the overall project product ensure that the agreed result has actually been realized.
Training on how to use the product and the remedy of errors that occur during operation within a certain period of time are usually part of the scope.