Do a test: control the scope.
What is a scope creep? Some examples.
The scope refers to the what is implemented in the project. This includes, for example, the products, services or results that the project aims for. This is based on the requirements – so customers’ requests for the product under development. Often, lots of requirements slip into the project scope because the customers put forth some new requests “whilst you’re at it – could you also add another new feature?” for example. Or your development team is working too quickly and implements another feature that wasn’t agreed upon. A scope creep arises. The workload unwittingly increases and more features are developed without previous consultation. A scope creep is a danger for every project that should be stopped or kept under control.
Definition of “scope creep” from the (PMBOK® Guide):
A scope creep is “adding features and functionality (project scope) without addressing the effects on time, costs, and resources, or without customer approval”.
Stop and control scope creep
Normally scope creep can’t be stopped entirely, so it’s more important to be able to control it.