COMPEL Glossary / scope-creep
Scope Creep
Scope creep is the uncontrolled, incremental expansion of a project or engagement's requirements beyond its originally agreed boundaries, typically occurring through a series of individually reasonable additions that collectively consume disproportionate time, resources, and budget without corresponding value.
What this means in practice
In AI transformation, scope creep is particularly common because AI projects frequently reveal unexpected data quality issues, integration complexities, and stakeholder requests that expand the work. For practitioners, managing scope creep requires clear scope documentation, formal change control processes, and the professional discipline to have difficult conversations with clients about what is and is not included in the engagement. In COMPEL, scope management is covered in Module 2.4, Article 9 on troubleshooting and recovery, with the scope change process being a core engagement governance mechanism.
Why it matters
Scope creep is particularly common in AI transformation because projects frequently reveal unexpected data quality issues, integration complexities, and stakeholder requests that expand work. Individually reasonable additions collectively consume disproportionate time and budget without corresponding value. Managing scope requires clear documentation, formal change control, and the professional discipline to have difficult conversations about engagement boundaries.
How COMPEL uses it
Scope management is covered in Module 2.4, Article 9 on troubleshooting and recovery during the Produce stage. The Model stage establishes clear scope documentation and formal change control processes. The Governance pillar enforces scope change procedures as a core engagement governance mechanism. The Evaluate stage assesses whether scope changes delivered proportional value to justify the additional investment.
Related Terms
Other glossary terms mentioned in this entry's definition and context.