Project Scope Management

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.

The Project Scope Management Plan is a component of the Project Management Plan that describes how the scope will be defined, developed, monitored, controlled, and verified.

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
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
Product scope are the features and functions that characterize a product, service, or result.

Scope Management Processes (PMI)

Project Scope Management

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

Collect requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

Define Scope

Define scope is the process of developing a detailed description of the project and product.

Create WBS

Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.

Validate Scope

Validate scope is the process of formalizing acceptance of the completed project deliverables.

Control Scope

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

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.

29 Comments

  1. Thank you for the templates, they helped me a lot.
    Isn’t the WBS typically generated by a software? What software would you recommend?

    BR
    Anthony

  2. The WBS can be generated using project management software. However if for some reason there is no software used, than you may create the WBS in Word, Excel etc. and possibly import it to your planning software afterwards.
    The type of software depends to different factors. In Middle East Primavera is very common in construction industry and sometimes even a clients requirement. There are many software packages including free downloadable open source. The right software maybe chosen according to project needs.

    Best regards
    Marc
    http://armaco.org

  3. @Habib,
    Thank you for your feedback, I hope the templates are of help for you. Once in a while visit our site again. I am trying to add more templates.

    @Alfredo,
    There are no stupid questions, but stupid answers.
    @Marijana,
    The definition for WBS according to the PMI is

    The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
    This means that the project is divided into smaller parts. This division often extends over several levels and there are different approaches that differ from project to project.

    If think for example of building a house, then we might subdivide into design, earthworks, basement, ground floor, …, roof, wiring, plumbing, HVAC, finishing, landscaping, etc. …
    These work packages can be further divided if it makes sense and finally include activities that are necessary to produce that package.
    For the client e.g., it might make sense to break up into sub-contractors.
    The main purpose is to estimate time, cost and resources.

    Best regards,
    Marc
    http://armaco.org

  4. Really nice templates, I find them very useful.
    I would like to see even more of them. Firstly they are userfriendly and second they gave me better understanding of what information should be provided in each plan.

  5. @Marc, thanks for the templates, they will be really helpful in my work

    @Marijana, the WBS is a breakdown of the requirement to simple levels where you can allocate time and money, and that you can clearly monitor.

  6. I believe this is among the such a lot vital information for me.

    And i’m satisfied studying your article. But want to
    commentary on few general issues, The site taste is perfect, the articles is truly excellent
    : D. Excellent job, cheers

  7. It’s really a cool and useful piece of information. I am happy that you shared this helpful info with us.
    Please keep us informed like this. Thanks for sharing.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.