Friday, Jul 30th

Last update08:13:38 PM GMT

You are here Scope Management

Change Control

change-controlI have recently been participating in a Linkedin discussion about re-occurring issues that create problems for project managers. Included in the top five list is “Scope Creep.”  It can also be called something else, depending on your emotional state at the time.

Before any project is started several key things take place.  A project is outlined by creating a detailed plan defining the scope of work.  This attempt to predict the future is called a baseline project plan.

Once the project has started any change to the original scope of work has a potential to negatively impact quality, schedule and cost.   Fact is, change happens and having an effective change management process is a key factor for success.

What is Scope? What should it be?

 I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to definitions of scope. I want to comment on it here because I think it’s an area that a lot of us have trouble with – both understanding and managing it.

Collaborative Techniques For Defining Project Scope

The creation of a Project Scope Statement doesn’t need to be a daunting task. Through the use of collaborative decision making and facilitated meetings techniques, it is realistic to build the components of the scope statement while gaining alignment from all project stakeholders in as few as two (2) days. The alignment gained from this upfront scoping effort will form the foundation for success throughout the remainder of the project. The key to this dynamic activity is effective planning and execution of a Project Scope Facilitate Meeting, using collaborative JAD techniques, to build the necessary scope outputs for a project.

Developing a Complete Project Scope Statement in 2 Days

scopeThrough our experiences working with project teams in many industries on hundreds of projects, we come to recognize a common pattern. Although Project Managers and project teams understand the theory and value of developing a Project Scope Statement, many do not have workable tools, techniques or processes for creating a Scope Statement. We have encountered Project Managers who have attempted to write the Project Scope Statement on their own or assigned this effort to a team member. Often, they move forward with a scope statement completed by one person and then route this scope statement to other stakeholders seeking input, buy-in, or approval. This process can take weeks and usually results in missing portions of key information needed to effectively manage scope on the project. More alarming to the overall project success is that there is minimal if any real buy-in and alignment on the scope of the project. In this situation, Project Managers are faced with spending too much time throughout the project trying to identify and manage scope creep due to unclear and uncommunicated project boundaries.  The creation of a Project Scope Statement doesn’t need to be a daunting task. This paper illustrates how to build the scope statement while gaining alignment from all project stakeholders in as few as two (2) days. The alignment gained from this upfront scoping effort will form the foundation for success throughout the remainder of the project. The key to this dynamic activity is effective planning and execution of a Project Scope Facilitate Meeting, using collaborative JAD techniques, to build the necessary scope outputs for a project.

Scope Control

The most prominent tool applied with scope change control is the Integrated Change Control System. Because changes are likely to happen within any project, there must be order to process, document, and manage the changes.

This system may include:

Page 1 of 2

  • «
  •  Start 
  •  Prev 
  •  1 
  •  2 
  •  Next 
  •  End 
  • »