Monday, 16 September 2013

Project Scope Management - PMBOK® Guide – Fifth Edition

Project Scope Management - Introduction

The Project Scope Management Knowledge area deals with collecting stakeholder requirements and then, defining the inclusions and exclusions for the project.

As important it is to include the right requirements, it is also important to not include requirements not stated by the customer. The scope statement takes care of the same - defining the project boundaries.

As part of defining the scope,  two aspects come to the fore:
1. Product Scope
2. Project Scope

Product Scope defines the characteristics and features of the product. Here, the product in the product scope is lop-sided. Since a project can create a product, service or result, the term product scope is meant to cover all these.

Project Scope not only includes the product scope but also the peripherals or other aspects involved in the phased development of the product - interim milestones, deliverables, processes, tools and techniques.

Note that collecting , defining requirements are all part of this knowledge area and gaining customer acceptance is also part of this knowledge area. Validate Scope process takes care of customer acceptance aspect.

Here are the processes in this knowledge area:

Planning Process Group:
1. Plan Scope management
2. Collect Requirements: Although many requirements might be collected from the stakeholders, only some of them can be included based on looking at different constraints like budget allocation, time factor etc. The defined project requirements become the scope.
3. Define Scope
4. Create WBS

Monitoring and Controlling Process Group:
1. Validate Scope - Monitoring 
2. Control Scope - Controlling


Project Scope Management Processes

Product V/s Project Scope

No comments:

Post a Comment