Part 1: Introduction
Case Study Request
Late last year I received a request to do a case study on scope control.
Scope Control or rather the lack of scope control is a problem we often run into, so I gathered my scope control best practices and documented them in this series of Scope Control Best Practices.
Why Best Practices Instead of a Case Study
Case studies pertain to a certain project. So with a case study on scope control we will only discuss the scope control issues that presented themselves in that particular project.
A best practices approach allows me to present all of the best practices that can be used on any project.
If you are interested in this series of best practices, please SIGN UP on this blog (to the right, if you have not already done so) to receive all the blog posts of this series delivered to your inbox.
Ok, let’s get started.
Scope Control Throughout All Phases of a Project
For scope control to be effective, it must be applied throughout all phases of a project. Scope control starts in the initiation phase and should be applied all the way to the closing phase of a project. Yes, even in the closing phase of a project. In this series we will discuss scope control in each one of the project phases.
Scope Control and Scope Creep
PMI’s PMBOK defines scope control as:
“The process of monitoring the status of the project scope and managing changes to the scope baseline”
and scope creep as:
“The uncontrolled expansion to project scope without adjustments to time, costs and resources”
So scope changes are OK, as long as they are managed. Scope creep however is a no no for us.
In the next part of this series, we will discuss scope control in the initiation phase of a project.