< >




Project Scope Management includes the processes required to ensure that the project consists of all the work required, and only the work necessary 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.

In the project context, the term scope can refer to:

    • Product scope. The features and functions that characterize a product, service, or result
    • Project scope. The work performed to deliver a product, service, or result with the specified features and functions. The term project scope is sometimes viewed as including product scope.

The processes used to manage project scope, as well as the supporting tools and techniques, can vary by project. The scope baseline for the project is the approved version of the project scope statement, work breakdown structure, and its associated work breakdown structure dictionary. A baseline can be changed only through formal change control procedures and is used as a basis for comparison while performing Validate Scope and Control Scope processes as well as other controlling processes.

The completion of the project scope is measured against the project management plan. The completion of the product scope is measured against the product requirements. The Project Scope Management processes need to be well integrated with the other processes so that the work of the project will result in the delivery of the specified product scope.


Entrance Criteria:

  • < >

Exit Criteria:

  • < >

Process and Procedures:

Tailoring Guidelines:


Process Verification Record(s):

  • < >
    • Stored By: < >


  • < >
    • Maintained By: <>
    • Submitted By: <>
    • Frequency of Submission: <>


  • Project Management Institute. (2013). A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition. Newtown Square, Pennsylvania: Project Management Institute