Scope creep

Technopedia Center

Faculty of Engineering and Computer Science
S1 Informatics S1 Information Systems S1 Information Technology S1 Computer Engineering S1 Electrical Engineering S1 Civil Engineering

faculty of Economics and Business
S1 Management S1 Accountancy

Faculty of Letters and Educational Sciences
S1 English literature S1 English language education S1 Mathematics education S1 Sports Education

Scope creep

From Wikipedia, the free encyclopedia

(Redirected from Functionality creep)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Scope creep" – news · newspapers · books · scholar · JSTOR (January 2022) (Learn how and when to remove this message)

Scope creep (also called requirement creep, or kitchen sink syndrome) in project management is continuous or uncontrolled growth in a project's scope, generally experienced after the project begins.^[1] This can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered harmful.^[2]^[3]^: 13 It is related to but distinct from feature creep, because feature creep refers to features, and scope creep refers to the whole project.

Common causes

[edit]

This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources in this section. Unsourced material may be challenged and removed.
Find sources: "Scope creep" – news · newspapers · books · scholar · JSTOR (January 2022) (Learn how and when to remove this message)

Poorly defined project scope

[edit]

Ineffective project management communication between a client and the project manager is a leading effect of project scope creep. An assignment that is not understood correctly will turn out to be completely different from clients vision. With that being said clients can also be to blame as they may not see a clear vision of what they want.^[4]^{[unreliable source?]}

Failure to capture all requirements

[edit]

Properly defining project scope requires thorough investigation by the project manager during the initial planning phase of a project. Failure to gather all information from all relevant stakeholders is a common reason for incomplete scope statements and missing requirements, which can frequently and easily lead to scope creep later in the project. It is essential that everyone on the team understands the project requirements thoroughly -- and that the project sponsor and relevant stakeholders have signed off on those requirements -- before execution of the project begins.^[5]

Lack of project management practices

[edit]

Adoptions and adhering to project management practices and project management processes are confirmed methods of preventing scope creep from dismantling the project.

Addition of unnecessary features

[edit]

Sometimes project teams tend to start adding additional features in order to impress the client.^[6]^: 482 This may not work and tend to cause more work for such project and throw off the scope.

The communication gap between project stakeholders

[edit]

Another huge cause of scope creep is the communication gap between the stakeholders. Clients may not respond quickly enough to the project managers causing the project to run into a bottleneck.

These aspects can affect the operational efficiencies of companies, especially when involved in long-term relationships.^[7] 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.