SCJP, SCJD, SCWCD, SCBCD
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Lasse Koskela wrote:I think the contract should be written in such a manner in the first place that renegotiating the content or delivery date does not require rewriting the contract. In other words, the contract should allow for changes.
SCJP, SCJD, SCWCD, SCBCD
a client who allows changes to a contract. But is that realistic? I haven't seen such client.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Lasse Koskela wrote:Note that I didn't say changes to the contract. I'm referring to one contract allowing changes in what is being developed under that contract. And it is business as usual for my company (a software consultancy).
SCJP, SCJD, SCWCD, SCBCD
Darya Akbari wrote:
Lasse Koskela wrote:I'm referring to one contract allowing changes in what is being developed under that contract.
But anyway, don't you have to negotiate the new requirements that arise during your project? Or how do you charge your client for your extra work?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Lasse Koskela wrote:
You might want to check out some of the links regarding "agile contracts" that I've bookmarked into del.icio.us.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Lasse Koskela wrote:Yes, the "requirements" are negotiated during the project. That's the whole point - we don't want to write a contract that prevents this negotiation from happening. Or, we don't want to renegotiate a contract just to renegotiate requirements.
The contract is about the business relationship between two companies. The requirements are about what the two companies build within that relationship. By mixing the two into a contract, we would be simply creating a dysfunctional relationship - one where the two companies' interests are constantly clashing.
You might want to check out some of the links regarding "agile contracts" that I've bookmarked into del.icio.us.
SCJP, SCJD, SCWCD, SCBCD
Darya Akbari wrote:How do you sell a optional scope project to a new client who want to hear a fixed price from you? How do you sell an optional scope contract when there are others (your competitors) who give a razor sharp fixed price to the client.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Darya Akbari wrote:How do you sell a optional scope project to a new client who want to hear a fixed price from you? How do you sell an optional scope contract when there are others (your competitors) who give a razor sharp fixed price to the client.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Lasse Koskela wrote:I'm not saying it's easy to get these kinds of contracts. It might require a fixed-everything contract to get that relationship started. Once the client understands that you're not trying to screw with him, and when he's seen the quality and integrity of your work, he's that much more comfortable with the idea of not fixing everything in a contract. And one day, you'll be able to sell an optional scope project to that client.
SCJP, SCJD, SCWCD, SCBCD
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |