Originally posted by BlasterBates
View Post
I've worked on Fixed Price before and although in theory that sounds fine (tests passed = implied acceptance = payment trigger), it usually ends up in a bunfight with the system integrator over how many tests and which ones are included in scope. If you can't define your deliverables up front, then accurately defining the tests to pass would be near impossible?
You're right though about scope creep, it makes change control even more important. Oh the fun we had arguing whether an issue was a defect or a CR, and the man hours we wasted doing so....

). That being said, you need to take a very conservative approach with your estimates, agree the acceptance criteria, as far as possible and, above all else, you need to have a degree of mutual trust. If either party wants things to go south (e.g. client trying to get something on the cheap, rather than fixing a budget), they will. A little experience goes a long way in judging a client and negotiating a FFP (it's an art as much as a science), but you have to start somewhere, and I think the OP is on the right track.
Comment