”Scope creep”, also known as feature creep or requirements creep, is defined as unexpected changes or additions to the requirements of an already approved project.

By adding unexpected effort and costs to a project, scope creep can derail a technology initiative significantly diminishing the chances of success. Some of the harmful affects of scope creep are as follows:

• Unexpected project resource requirements



• Extended project timelines



• A significant increase in overall project costs



• Invalid project assumptions that can invalidate existing requirements



• Strained client / vendor relationships

But despite the perils of scope creep, it is extremely common to technology projects, both large and small.

So, why is scope creep so common and what steps can be taken to avoid it?

Scope creep is usually the result of a failure to effectively define the assumptions and requirements of a project prior to project signoff and commencement. This occurs for any number of the following reasons:

• A failure to clearly define business objectives



• A failure to involve all affected parties during the requirements definition phase



• A failure to identify all affected legacy and 3rd party information systems



• A rush to get project and budget approval



• A failure to define requirements at a sufficiently low level

However, scope creep is not always a bad thing. There are cases where scope creep cannot be predicted and can actually produce positive outcomes.

If business requirements unpredictably change during the life of a project, scope creep becomes an unavoidable reality.

In cases where new opportunities are identified during the life of a project, as long as the incremental payback outweighs the additional project costs, scope creep can actually add to the project’s return on investment. In these cases, it is important that effective change management processes be in place in order to effectively evaluate the value of the proposed changes and integrate the new requirements into the project.

However, scope creep is far more often both avoidable and costly. There are a number of strategies that can be employed at the outset of a project in order to avoid bad scope creep (as well as effectively manage good scope creep), including the following:

• Properly define business objectives



• Clearly define what is in play and what is not



• Have well-defined project management and change management strategies



• Involve all stakeholders in the project requirements definition phase



• Identify all affected legacy and 3rd party systems



• Develop a thorough functional specification for the project

While these strategies cannot completely eliminate the chances of scope creep, they put an organization in a position to effectively deal with it and potentially even profit from it.


Datapro Technology Solutions is an IT consulting firm that helps small and medium-sized businesses get the most from their investments in technology.

To find out more about the services we provide and how we might be able to help your business, visit our web site at dataproforbusiness.com or give us a call at 416-977-1991.