Agile development

<p>It is proposed as an alternative to <a class="wikilink" href="/waterfall_development/">waterfall development</a></p> <ul> <li>Individuals and interactions over processes and tools</li> <li>Working software over comprehensive documentation </li> <li>Customer collaboration over contract negotiation</li> <li>Responding to change over following a plan</li> </ul> <p>It aligns with the <a class="wikilink" href="/lean_methodology/">lean methodology</a>, incorporating <a class="wikilink" href="/customer_feedback/">customer feedback</a> into future development, in close iteration loops called <strong>sprints</strong>. Each sprint delivers a <em>usable</em> MVP that allows to collect feedback. </p> <ul> <li>Incremental testing and correction</li> <li>Validate customer interest</li> <li>Build the right product for the customer <strong>BUT</strong></li> <li>Higher demand on product managers</li> <li>Intense attention on regular basis</li> <li>Constant deadlines (as opposed to thinking deeply)</li> <li>Reactionary instead of strategic</li> </ul>