I am soliciting input on opinions for the best way to handle changes to the Scope Statement. One side of our group, and I shall refer to them as "tastes great", say that you change the Scope Statement and attach the approved Change Request to the back. The "less filling" group says you turn on "track changes" in Word, and that way everybody knows what it WAS, as well as what it NOW IS. How are you guys doing this? Is it "tastes great", "less filling" or is it really a Rocky Mountain high?
Use version control on your documents. This will make it easy to track the changes. If the project is well underway (80% of the requirements have been documented and agreed to) then all changes to scope should be tracked using a Change Management process. Saving Changes...
I do endorse Christi in that Version Control if fundamental for Scope Control. The less filling group assume that a passive measure such as change tracking in a document is a good quality strategy - I strongly believe it is not. Where are the approvals, and where is the evidence that all have been informed? Where is the version control?
But I would add that Scope Change starts from the very first iteration of the Scope Document - and in that regard I would advocate the use of Change Requests from the outset not just during the implementation stage.
If you would like to discuss examples of change requests from my OZ experience, please email me.
Regards, David Hudson, Brisbane, OZ Saving Changes...
