rocknbil - 5:25 pm on Nov 21, 2009 (gmt 0)

Good approach, my two cents on change of scope . . .

The problem with change of scope is that a project will get off on tangents and take more time than allotted. This makes it extremely difficult to schedule in other projects, and keep everything to deadlines. This becomes extremely relevant when you're juggling several projects at once.

The other problem is in the client vision versus reality. When they see their vision materialized, they may begin thinking "it would be better if we did it this way" or "now that I see it, it's worthless without this or that functionality." So now we're off on what is basically a sub-project, further complicating scheduling.

I resolve this by clearly defining scope, and when the second issues come up, say "be glad to - but as a new project after this one is closed." The exception is if the project takes an entire new direction, in which case we close the project as is, re-submit new proposal.