Control and Monitoring
16 Scope Creep
The Project Management Institute defines scope creep as the “adding of additional features or functions of a new product, requirements, or work that is not authorized (i.e. beyond the agreed-upon scope)” (Larson & Larson, 2009). Scope creep can be very harmful to a project by causing delays, additional costs, and hurt customer or team relationships.
In projects where the scope is poorly defined, the chance of scope creep is increased. The Digital Project Manager details several causes of scope creep, as well as strategies for managing it:
Causes of Scope Creep
- The initial scope is ambiguous
- Scope and requirements are not managed
- Inconsistent process for collecting product requirements
- Lack of sponsorship and stakeholder involvement
- Project length not determined
Managing Scope Creep
- Be proactive
- Prioritize
- Be transparent
- Analyze impacts
- Embrace it
Adding additional features or functions of a new product, requirements, or work that is not authorized.
The extent of what a project will produce (product scope) and the work needed to produce it (project scope).
