Fixed price, fixed scope development contracts are still a very relevant and are not likely going away. Clients want a to know how much they are going to spend and exactly what they are going to get. The reality is, iterative development was created because they don’t know (entirely) what they want up front. Waterfall is still primarily used, however the reality is, it’s more of a business decision than a development decision.
Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.
Same old story…We spend a great deal of time up front gathering business requirements and attempt to create a specification of our interpretations of those requirements. We then learn new requirements which result in change requests. Changes are generally viewed negatively during waterfall, even though they are getting the customer closer to the solution they want. During implementation, there should be no business logic decisions to be made by the developers, right? We should of defined all of this in our specification. Ya right. After implementation, testing, and delivery, our customers get their working software. What is their reaction?
This isn’t working they way we wanted.And then our response:
Yes it is. Look at the specification.This turns into meeting after meeting with no one happy.