Scope creep

Scope creep (also called requirement creep, function creep and feature creep) in project management refers to uncontrolled changes or continuous growth in a project’s scope. This can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered harmful.^{[1] [2][3]}

If budget, resources, and schedule are increased along with the scope, the change is usually considered an acceptable addition to the project, and the term “scope creep” is not used.

Scope creep can be a result of:

• poor change control
• lack of proper initial identification of what is required to bring about the project objectives
• weak project manager or executive sponsor
• poor communication between parties
• lack of initial product versatility

Scope creep is a risk in most projects. Most megaprojects fall victim to scope creep (see Megaprojects and Risk). Scope creep often results in cost overrun. A value for free strategy is difficult to counteract and remains a difficult challenge for even the most experienced project managers.

See also

• Anti-pattern
• Cost overrun
• Instruction creep
• Mission creep
• Software bloat

References

1. "The 7 Deadly Sins of Scope Creep". roberthalf.com.
2. "Scope Creep – The Two Dirtiest Words in Project Management". teamgantt.
3. "Scope Creep: What Is It? Why Is It So Creepy? And How To Avoid It". Datapro Technology Solutions.

External links

• A Comprehensive Series on Scope Creep
• Wideman Comparative Glossary of Project Management Terms by R. Max Wideman P.Eng. FCSCE, FEIC, FICE, Fellow PMI