In the engineering world, we call this "Proposed Scope"
We look at Scope changes (feature creep) as a good way
to increase the budget (often at premium prices).
When the scope changes, so does the budget. I always
revise the written proposal for a website to reflect the
scope change.
Of course, you probably mean by "feature creep" allowing
the scope to change without changing the terms of the
proposal. I agree: This is a no-no. But your client
must be allowed to change his/her mind. You just have
to be professional and let them know the cost. Then they
can decide what they want to do.
This is why we write proposals to define the deliverables
as accurately as possible: To be able to identify when a
new feature is not included in the scope we proposed.
It's a pain to do, but it saves much pain later....
If the new feature's in the grey area, we call it the
client's way so we're sure we learn our lesson and don't
make the same mistake again (hopefully).
We typically write a paragraph for each page in the
proposed website. Sometimes we need more than one paragraph.
We also get 25% of the budget up front before we start.
best, paul
At 11:40 AM 11/1/00 -0600, you wrote:
>your phone should be unplugged, but also because feature creep should have
>been disallowed to the client in the first place).
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
