Project Management Process Scope

Greetings from Customer

In the methodology noticeably the project scope statement and managing the scope (Scope Management) is missing. Which process will take care of these.

This is covered in the “Change Management” section. Please have a look and let me know if you have any questions.

Change management comes into play once the entire requirement (Scope) is defined, and the changes will be to the original requirements. The Project Charter defines the requirements, but rather it is at high level, a detailed specification has to be done, which different people may call it different names (Project Scope Statement as per PMI, Requirement Specification, Functional Specification). Furthermore scope is one of the triple constraints therefore defining it entirely and controlling is very much essential.

I could not find that in the templates provided in MPMM Project Management Process. I am sure this question would have come up in the past from other customers. As per PMI scope is further divided as ‘Preliminary Scope Statement’, ‘Scope Statement’ reemphasizing the important of this requirement.

I understand this is correct. We don’t have specific templates that define and manage scope. However our change management templates overlap with scope management a lot. Please have a look here Change Management Templates for the overlap between the PMI scope processes and our templates. Please let me know if you have any further questions. We are here to help.

Join our RSS feed

Click here to join our feed and get the latest articles, every day!