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.
About The Advisor
Dr. Joseph Sweeney is an IBRS advisor specialising in the areas of workforce transformation and the future of work, including; workplace strategies, end-user computing, collaboration, workflow and low code development, data-driven strategies, policy, and organisational cultural change. He is the author of IBRS’s Digital Workspaces methodology. Dr Sweeney has a particular focus on Microsoft, Google, AWS, VMWare, and Citrix. He often assists organisations in rationalising their licensing spend while increasing workforce engagement. He is also deeply engaged in the education sector. Joseph was awarded the University of Newcastle Medal in 2007 for his studies in Education, and his doctorate, granted in 2015, was based on research into Australia’s educational ICT policies for student device deployments.