1–8 of 8 posts
Why I don't give fixed price. Software developer story.
a.khavr.com
Fixed bid should mean fixed scope (fixed in STONE), with all change requests in writing and done on an hourly basis.
The only spec that's is not subject to interpretation is the software itself. Otherwise it all boils down to relationship between the customer and the developer: personal trust, etc. And, of course, this creates immense place for psychological games, which mostly are lose-lose kind of game.
Fixed bid should mean fixed scope (fixed in STONE), with all change requests in writing and done on an hourly basis.
It should, but it almost never does. The only spec that's is not subject to interpretation is the software itself. Otherwise it all boils down to relationship between the customer and the developer: personal trust, etc. And, of course, this creates immense place for psychological games, which mostly are lose-lose kind of game.
Earlier quoted context omitted.
It should, but it almost never does. The only spec that's is not subject to interpretation is the software itself. Otherwise it all boils down to relationship between the customer and the developer: personal trust, etc. And, of course, this creates immense place for psychological games, which mostly are lose-lose kind of game.
If the client's playing games, don't give them an inch. It will never end well if you do.
You have to be reasonable if you expect good relations with someone. The developer should provide a higher estimate that provides a buffer for the uncertainty involved. Get a written spec before signing the contract.
Earlier quoted context omitted.
If the client's playing games, don't give them an inch. It will never end well if you do.
Sounds like this guy just doesn't want to waste time. You have to be reasonable if you expect good relations with someone. The developer should provide a higher estimate that provides a buffer for the uncertainty involved. Get a written spec before signing the contract.
:)
> You have to be reasonable if you expect good relations with someone. The developer should provide a higher estimate that provides a buffer for the uncertainty involved. Get a written spec before signing the contract.
Exactly. (Although if the client agrees to a certain project scope, I don't mind writing the spec for them to sign off on). The other side of it is, good clients should get more wiggle room, but you've got to have a strategy for avoiding horror stories.
Earlier quoted context omitted.
If the client's playing games, don't give them an inch. It will never end well if you do.
Sounds like this guy just doesn't want to waste time. You have to be reasonable if you expect good relations with someone. The developer should provide a higher estimate that provides a buffer for the uncertainty involved. Get a written spec before signing the contract.
I am still quite can't imagine a rational customer agreeing to pay such premium. Perhaps this is my chance to make a fortune :)
Fixed bid should mean fixed scope (fixed in STONE), with all change requests in writing and done on an hourly basis.