Editing Agile software development (section)

===Iterative, incremental, and evolutionary===
Most agile development methods break product development work into small increments that minimize the amount of up-front planning and design. Iterations, or sprints, are short time frames ([[timeboxing|timeboxes]]){{sfn|Project Management Institute|2021|loc=2.3.3 Development Approaches}} that typically last from one to four weeks.{{sfn|Rubin|2013}}{{rp|20}} Each iteration involves a [[cross-functional team]] working in all functions: [[Project planning|planning]], [[requirements analysis|analysis]], [[Software design|design]], [[Computer programming|coding]], [[unit testing]], and [[acceptance testing]]. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the product to adapt to changes quickly.{{sfn|Project Management Institute|2021|loc=§3.12 Enable Change to Achieve the Envisioned Future State}}<ref name="auto">{{cite book | author=Moran, A.|title=Agile Risk Management |publisher=Springer Verlag|year=2014|isbn=978-3319050072}}</ref> An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal [[Software bug|bugs]]) at the end of each iteration.<ref name="embracing change">{{cite journal|
last=Beck|first=Kent|
year=1999|title=Embracing Change with Extreme Programming|
journal=Computer|volume=32|issue=10|
pages=70–77|
doi=10.1109/2.796139}}</ref> Through incremental development, products have room to "[[Fail-fast system|fail often and early]]" throughout each iterative phase instead of drastically on a final release date.<ref>{{Cite journal|last=Mergel|first=Ines|date=July 2016|title=Agile innovation management in government: A research agenda|url=https://linkinghub.elsevier.com/retrieve/pii/S0740624X16301101|journal=Government Information Quarterly|language=en|volume=33|issue=3|pages=516–523|doi=10.1016/j.giq.2016.07.004}}</ref> Multiple iterations might be required to release a product or new features. Working software is the primary measure of progress.<ref name="ManifestoPrinciples" />

A key advantage of agile approaches is speed to market and risk mitigation. Smaller increments are typically released to market, reducing the time and cost risks of engineering a product that doesn't meet user requirements.