Main

Conclusion: A common mistake when engaging third-parties for ‘Agile software development services’ is to use a contract or procurement approach that is at odds with the tenets of Agile software development. In cases where contract and payment terms follow the more traditional ‘fixed price and scope’ statements of work, organisations do not get true Agile development services, and more likely than not, will be frustrated and dissatisfied with results of the project. Instead, organisations should consider using specific styles of Master Service contracting agreements with Agile developers, or accept that the best than can be achieved will be a hybrid “Watergility” approach by the developers.

Existing Client Login



This Advisory paper is only available to IBRS Advisory clients. To find out more about becoming an IBRS Advisory client complete the attached form and we will be in touch.
Please let us know your name.
Please let us know your email address.
Please enter a valid phone number
Invalid Input

Register to read more...

Sitemap