One of the biggest challenges of delivering projects on time and budget is scope creep. Scope creep occurs when a change is made to the whole or part of the project when the project is already underway. (Wikipedia, n.d.) Defined scope creep as uncontrolled changes or continuous growth in a project's scope. Scope Creep has the tendency of resulting in poor change control, cost overrun, weak management, and lack of project versatility. There are many reasons for why scope creep occurs.
For example:
  • Underestimating the Complexity of the Problem: Scope creep may occur because the project is new and was never done before.
Nobody knows what the output of the project should be like, no lessons learned.
  • Communication: Poor communication between client and designer can lead to scope creep.
  • Poor Requirements Analysis: Customers provide a vague idea because they don't always know what they want.
Few ways of minimizing the impact of scope creep are:
  • Create a scope statement that shows the entire scope of the project and make sure that it is signed off by all the clients to ensure that they are aware of what the outcome of the project would be
  • If the customer requests a change in the middle of the project, first an analysis of cost -benefit should be conducted, and discuss with the stakeholders what are the required changes and the impact of the changes.
  • All changes and the effects of changes like cost overrun, time should be written and signed off by the stakeholders.
  • Understand what the customer wants and analyze what the client needs, Collaborate with the stakeholders to discuss the scope of the project.
(Standish, CHAOS Manifesto, 2013)The report shows that the users never used 45% of the delivered features. Thus "satisfying" adding features that are required and add business value instead of "gold plating " adding bells and whistles (features) that do not add business value can reduce scope creep.