Scope Management In PMP Projects

Project scope management is one of the most significant knowledge areas that we have in PMBOK sixth edition. The scope management knowledge area is about how we define the scope of the project, how we are controlling it and what kind of output we are trying to create by the end of the project, what outcomes are we trying to achieve for our stakeholders and what benefits of the project that we are trying to help our stakeholder achieve or the result or the outcome that we are working for.

Whenever we work on a project what we get by the end of the project is one or more deliverables. The deliverable could be in the form of some physical product that you're planning to make available in the market or the deliverable could be in the form of some service or some result that you are producing. That result or that product is going to help your stakeholders achieve the outcomes that they aimed to have. There could be various outcomes that they want to achieve by the way.

For example if you are making available a product in the market for your stakeholders, You and your team should ensure that they produce the deliverables in line with the expectations that are agreed upon between the team and the stakeholders and obviously as a team we should also be knowing the kind of benefits that the project offers to the stakeholders. That's how these all are interlinked with each other.

When speaking about scope, we have to look into the product scope and the project scope. There is a product life cycle and there is a project life cycle. When we produce any product we basically undertake some project and the outcome of the project is your product. However once you start working on that product, the product life cycle is much much longer and within life cycle of a product you might be undertaking multiple projects.

There are certain tailoring considerations for each of the knowledge areas in PMBOK. It is important to know what are the tailoring considerations under scope management. A single solution doesn't fit all so we'll have to tailor the process that we are working on. If I have to work on a scope management I might have to tailor the process based on the context I am working in and that really differs according to the sector which you're working on. Because the context is different you're dealing with different kinds of stakeholders so it's very important for us to tailor the process based on the context that you're working in.

There is not much of a difference between PMBOK sixth and fifth edition from scope management point of view. Of course there are certain changes that have been done in the form of tools and techniques, in the form of certain suggestions like usage of certain techniques in comparison with some of the other knowledge areas. We don't know yet what PMBOK 7 will bring when it is published.

Under each of knowledge areas you'll find various processes. Speaking of scope management we start with plan scope management and this is where we focus on how to plan the scope management activities on project. Collecting requirements is definitely one of the important process where we reach out to the stakeholders to identify their needs and requirements based on the project or product that we are working on. Then based on the requirements that we have gathered before, we define scope and we ensure that whatever it is defined in the scope you only work on those items and not something which is not part of scope. Creating WBS process certainly gives us an idea about what are the low level activities, tasks, work packages that we have to work around and decomposition is one of the techniques that is used while creating WBS. Creation of WBS is definitely one of the important processes within the scope management.

After this, we have to validate scope against the acceptance criteria. That is defined between you and the customer for each deliverable that you are producing by the end of each phase in project or product lifecycle. It's important to define very clearly the acceptance criteria and then lastly we have got control scoop and this is where we basically see how do we control effectively the changes that might happen to the scope and how do we go about managing those changes so these are the six processes that we have within scope management.

There are six processes in Scope Management Knowledge Area: