Scope management is the greatest challenge in project management.

When I manage scope during a project I pay close attention to keeping scope in control using the outline given in chapter 5 of the Guide to The Project Management Body of Knowledge (PMBOK Guide). In this blog, I will address an overview of things I do to management changes to project scope.

Controlling project scope is making sure the project has all the work required in it to be successful complete the project, and that no unnecessary work is involved. Scope Management in the Planning Processing Group Phase includes: Collecting Requirements, Defining Scope, and Creating the WBS. During the Monitoring and Controlling Process Group Phase scope is managed by verifying the scope, and controlling the scope.

Knowing what is needed to manage scope impacts my understanding of other key "Knowledge Areas," and is "part of the Development Plan process ( (Project Management Institute, 2008, p. 104)." 104)". I always knew that scope control was an issue during projects, but I never realized how negatively scope changes impacted all other phases of a project until I paid attention to it. When you learn scope management, you will be able to recognize when scope changes and how to correct this change to keep the project on track.

According to the PMBOK "The scope management plan may be formal or informal, highly detailed, or broadly framed, based on the needs of the project." I am beginning to believe the scope management plan should always be formal but differ in its detail. I have run my own company for 16 years, and I will always have a formal scope management plan just for the simple fact of keeping everyone, and every project focused on the project at hand.

Too many people do not define the scope at all. Their approach is: here is what I want to do, how, and I going to do it, the benefits will be this, and when a fire starts I will put it out.

PMBOK tells us defining the scope includes using inputs such as project charter, requirements document, and organizational process assets. PMBOK mentions the following tools, and techniques used to control scope as: using expert judgment, product analysis, alternative's identification, and facilitated workshops. All of these techniques will help you control scope in the future.
Project Management Institute. (2008). A Guide to the Project Management Body of Knowledge PMBOK Guide (4th ed.). Newtown, PA: Project Management Institute, Inc.