Editing Agile software development (section)

====Lack of overall product design====
A goal of agile software development is to focus more on producing working software and less on documentation. This is in contrast to waterfall models where the process is often highly controlled and minor changes to the system require significant revision of supporting documentation. However, this does not justify completely doing without any analysis or design at all. Failure to pay attention to design can cause a team to proceed rapidly at first, but then to require significant rework as they attempt to scale up the system. One of the key features of agile software development is that it is iterative. When done correctly, agile software development allows the design to emerge as the system is developed and helps the team discover commonalities  and opportunities for re-use.<ref>{{cite book|last1=Beck|first1=Kent|title=Extreme Programming Explained|date=2000|publisher=Addison-Wesley|isbn=978-0201616415|pages=[https://archive.org/details/extremeprogrammi00beck/page/48 48–49]|url=https://archive.org/details/extremeprogrammi00beck/page/48}}</ref>