The Agile Manifesto is a philosophical touchpoint for all agile software development (ASD) methods. We examine the manifesto and some of its associated 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 and important impacts. Firstly, the reduction in iteration durations and secondly, the push for reduced levels of documentation (especially in relation to software requirements). Other aspects of the Agile Manifesto may not have exerted a significant impact; for example, the use of tooling to automate processes has become central to continuous software engineering (CSE) and may not be wholly congruent with the manifesto. Furthermore, many organisations may still rely on business contracts despite calls in the manifesto for greater levels of informal customer collaboration.