Social:Scope creep
Scope creep (also called requirement creep, or kitchen sink syndrome) in project management is continuous or uncontrolled growth in a project's scope, at any point 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
 | This section needs additional citations for verification. (January 2022) (Learn how and when to remove this template message) |
Poorly defined project scope
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
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
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
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
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.
See also
- Anti-pattern
- Cost overrun
- Scope (project management)
- Planning poker
- Escalation of commitment
- Instruction creep
- Mission creep
- The Mythical Man-Month
- Second-system effect
- Software bloat
References
- ↑ Lewis, James (2002). Fundamentals of Project Management (Second ed.). AMACOM. pp. 29, 63. ISBN 0-8144-7132-3. https://archive.org/details/fundamentalsofpr00lewi_1/page/29.
- ↑ Kendrick, Tom (2015). "Chapter 3. Identifying Project Scope Risk". Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project (3rd ed.). AMACOM. pp. 50–52. ISBN 978-0-8144-3609-7. https://books.google.com/books?id=BnuZBgAAQBAJ&pg=PA52.
- ↑ Sanghera, Paul (2019). PMP in Depth (Third ed.). Apress. ISBN 978-1-4842-3910-0.
- ↑ "Managing Scope Creep in Project Management" (in en-us). February 22, 2023. https://www.villanovau.com/resources/project-management/project-management-scope-creep/.
- ↑ Guerrero, Felicia, PMP. "What is Scope Creep and How Can You Control It?". https://becomeaprojectmanager.com/what-is-scope-creep-and-how-can-you-control-it/.
- ↑ Sanghera, Paul (2019). PMP in Depth (Third ed.). Apress. ISBN 978-1-4842-3910-0.
- ↑ Invernizzi, Diletta Colette; Locatelli, Giorgio; Brookes, Naomi J. (2018-07-04). "The need to improve communication about scope changes: frustration as an indicator of operational inefficiencies". Production Planning & Control 29 (9): 729–742. doi:10.1080/09537287.2018.1461949. ISSN 0953-7287. http://eprints.whiterose.ac.uk/129889/1/The%20need%20to%20improve%20communication%20Invernizzi%20Locatelli%20Brookes%202018.pdf.
 |  |
