<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Software project management - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Software_project_management&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_project_management&amp;p=3">3.Next</a>
</p>
<p>and circuitry. To manage new development efforts, companies applied the established project management methods, but project <a href="page.php?w=Schedule_%28project_management%29">schedules</a> <a href="page.php?w=Project_slippage">slipped</a> during test runs, especially when confusion occurred in the gray zone between the user specifications and the delivered software. To be able to avoid these problems, software project management methods focused on matching user requirements to delivered products, in a method known now as the <a href="page.php?w=waterfall_model">waterfall model</a>.</p><p>
<a accesskey="1" href="page.php?w=Software_project_management&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_project_management&amp;p=3">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
