« Project Estimation Using “Use Cases”
Do You Have What It Takes to Be a Project Manager? »

It Is Your Job to Protect the Project Scope!

July 5, 2010 | Author: PM Hut | Filed under: Project Management Musings, Project Scope Management, Scope Management

It Is Your Job to Protect the Project Scope!
By Ron Rosenhead

Yes it is. Someone needs to do it, so why not you, the Project Manager! Protect the project scope!

Well, there are two major assumptions that need testing in the above words:

  1. Someone needs to do it: I am still coming across projects where the scope of the project is identified, agreed but not managed. So, whether you are a project sponsor, project board member, project manager or team member. Take responsibility and protect what has been agreed.

  2. Protect the project scope: Why bother? I have assumed of course that the scope of work has been agreed. If this is the case then the scope needs protecting. I see too many projects where scope creep seems endemic. (Scope creep, amending the scope of work to be done without an agreed process to check that the ‘new work’ is worth doing)

A lack of protection around the scope is a clear risk. It is also a governance one - who can make the decisions to change the project and how.

So, here is a simple process to help you manage scope creep or requests for change. It is by no means perfect and you will need to put your head above the parapet by suggesting completing of a change request form. Download a brief PowerPoint presentation here and some hard copy documents.

“Scope creep is a sick illness treatable only by saying no.” This quote came from a project manager who decided to challenge the ‘request’ from a senior manager to include something in the project. I suggested he should avoid saying NO but use the process. He did and focused on the process in the presentation and it worked!

Ron Rosenhead is a trainer, consultant speaker and coach all in the area of project management. He has vast consultancy and training experience and you can read his blog at http://www.ronrosenhead.co.uk

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

This entry was posted on Monday, July 5th, 2010 and is filed under Project Management Musings, Project Scope Management, Scope Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

1 person has left a comment

Hi Ron,

Fully agree. Project scope creep is a major issue in many projects, and agree that someone needs to take control, and responsibility.

In my view, that person has to be the project manager, supported by the governance structure in place. I agree that saying ‘no’ sometimes seems hard, but if the scope has been clearly defined and agreed, and a structured change control mechanism is in place, then the ultimate result may be ‘no’.

With best regards,

Ed

Dr. Edward Wallington wrote on July 5, 2010 - 1:36 pm | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories