Waterfall development
<p>The <a class="wikilink" href="/product_requirements_document/">Product Requirements Document</a> has to be very well defined and validated as much as possible for this type of development. An alternative is <a class="wikilink" href="/agile_development/">agile development</a>. </p>
<ul>
<li>It is very structured</li>
<li>Defined stages<ul>
<li>You only move from one stage to the next once the previous is completed</li>
</ul>
</li>
<li>Detailed specifications</li>
<li>All requirements are fully laid out</li>
<li>Budgeting is accurate</li>
<li>Less day-to-day management
<strong>But</strong></li>
<li>Maybe you don't fully know the requirements</li>
<li>It is difficult to make changes</li>
<li>Unknowns may impact timelines</li>
<li>Market conditions change during development</li>
</ul>
Comment
Share your thoughts on this note. Comments are not public, they are
messages sent directly to my inbox.