Yes it is. Someone needs to do it, so why not you! Protect the project scope!
Well, there are some major assumptions that need testing in the above words:
- 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.
- 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!
Get the presentation here and some free templates!