<?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="Scope creep - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Scope_creep&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Scope_creep&amp;p=3">3.Next</a>
</p>
<p>final product. Scope creep cannot be entirely prevented, so mitigating its harms is done by managing it after noticing it. Scope creep has at least some presence in every project, and it can endanger many of them. Scope creep is also known as requirement creep, kitchen sink syndrome, mission creep, or feature creep, with the last two relating especially to government/military projects and software projects, respectively. Sometimes, scope creep and feature creep are defined separately, with scope creep referring to scope enlargements and feature</p><p>
<a accesskey="1" href="page.php?w=Scope_creep&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Scope_creep&amp;p=3">3.Next</a>
</p>

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

</card>
</wml>
