Abstract:
The Agile Manifesto is a philosophical touchpoint for all agile software development (ASD) methods. We examine the manifesto and certain agile methods in an effort to identify the major impacts of ASD. We have encountered some difficulty in delineating agile and non-agile software processes, which is partially the result of terminological confusion. It is clear from the volume of published research that ASD has made a significant contribution, and we have identified two lasting impacts: a reduction in iteration durations and a push for reduced levels of documentation. We find that the contemporary use of tooling to automate processes may not be wholly congruent with the manifesto and that many organisations may still rely on business contracts despite calls in the manifesto for greater levels of informal customer collaboration.
