When Scope Change is Inevitable
Sometimes it becomes necessary that the scope must change and that you will find yourself in need of free tools. Managing scope change can be made easier by using templates for change requests and by using scope statement templates. Luckily, Bright Hub has such free templates in our media gallery.
Any time there will be a change to the scope of the project, you need to submit a scope change request. The scope change request should start out by describing the requested change. What are you changing in the scope, why are you changing it, and what will the impact of this change be on the work breakdown structure. Do not forget to take account of potential risks to the project due to the scope change in this document. The template for scope change requests is a very useful free tool.
Once your scope change request has been approved, then you're going to want to create a new scope statement that captures the changes of the scope. Your new scope statement should cover the whole of the changes being made in the project. You can create an effective scope statement using the template made available in the media gallery.
Finally, be sure you know the difference between scope creep and scope discovery. Before you submit any change forms, are the changes being made to your project necessary or are they really a product of scope creep? Don't be afraid to use the best free tool for managing scope change available: the word, "no."
Screenshots courtesy of Ronda Levine.