Project Scope Management

 

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.

(from PMBOK® Guide, Fifth Edition)

For you that are new to Project Management, how should you approach studying this Knowledge Area? It’s recommended to have quick review of what it is and how it interacts with other knowledge areas, and then an in-depth study of all its components and interactions.

Why is Scope Management the second Knowledge, Why is it so important?

Do you manage Scope in your real life projects?

If your answer is yes, then be honest to yourself, do you have a have proof of it?

Where is your Scope Baseline stored? If it is your baseline, it is already approved and communicated.

How often do you revise your scope baseline? And when you doing so, do you follow the Change Control Process?

Do you have a Change Control Process for your Scope?

What amazes you most about this Knowledge Area? Share your thoughts around this…

What's the most difficult task you face as a PM when dealing with this KA.

 This knowledge are is composed of the following processes:

Plan Scope Management—The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.

Collect Requirements—The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

Define Scope—The process of developing a detailed description of the project and product.

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

Validate Scope—The process of formalizing acceptance of the completed project deliverables.

Control Scope—The process of monitoring the status of the project and product scope and managing changes to the scope baseline.

(from PMBOK® Guide, Fifth Edition)

What’s exactly the Project Scope?

What’s exactly the Product Scope?

What’s the difference between Project Scope and Product Scope?

Which of these processes amaze you most?

What's the most difficult task you face as a PM when dealing with these process groups.

Important concepts related to scope:

Product scope. The features and functions that characterize a product, service, or result; and/or

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.

 (from PMBOK® Guide, Fifth Edition)

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 (WBS), and its associated WBS 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.

(from PMBOK® Guide, Fifth Edition)

Please post your answers/inquiries about this subject….