All software development contracts I've seen specify that x piece of software will be developed for y dollars within z amount of time. This works out for traditional Waterfall model projects, where you do a lot of forward planning and it is reasonable to expect that you will know how long the project will take near the beginning of the project. It doesn't match up at all for Agile, where you can start without having any idea exactly where you will end up and you are expected to be able to deal with requirements changes.

How would a contract for Agile software development differ from a contract for Waterfall software development? Is there a place where I can find a sample contract for Agile development?

  • In any way you like; the terms of a contract are whatever the parties agree (providing they are legal).
    – Dale M
    Commented Jul 24, 2015 at 23:20

1 Answer 1


Keep in mind that for a real project with real money on the line you should consult with a business lawyer who can tailor a form to the specifics of your project and team.

That said, this is the first google result for 'Agile Software Contracting' (and there are many others):

Agile Contracts
Contracting for agile software development is fundamentally different from traditional project contracting. Using traditional contracts for an agile development project can endanger the project execution and causes the company to fail to get the potential benefits of agile development.

The purpose of this page is to collect references to agile contracting to support organizations to change their contracting models, reduce risk and get more benefits out of adopting Agile development.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .