Project Creep

Uncontrolled changes in a project’s scope or Scope Creep is a risk in most projects. It can happen by a big amount of reasons but the main it’s not being aware of it.

So, I would like to review some tips about how to take care about it:


  1. Scope Management starts before the project starts,
  2. Be sure you understand the project vision through the major deliverables,
  3. Understand the priorities of the stakeholders,
  4. Review the Change management process with the client.


  1. Define your deliverables and have them approved by your client,
  2. Break the approved deliverables into actual work requirements. Break it again till you be sure about there is nothing lost or defined wrongly,
  3. Break the project down into major and minor milestones,
  4. Evaluate the project schedule as a director visualize a movie before to film it,
  5. In this evaluation check that you achieve the deliverables,
  6. Be sure the Project Definition is completed and communicated to all stakeholders before you start your project. Once it’s done, get the approval.


  1. Expect that there will be scope creep. It’s there!
  2. Educate the project developers about change management processes,
  3. Document your efforts before you begin them,
  4. Ensure that all team members are aware of the agreed-to scope and have read and understand the scope as documented in the Project Definition.

Monitoring and Controlling

  1. Remain alert to small, nonessential changes the team may be making informally, thinking that they are delivering better service to the customer or increasing client satisfaction.
  2. Scope changes, even small ones, need to be evaluated in light of their overall worth and their impact on delivering results on time and within budget.
  3. A small change late in the project usually requires unanticipated, extensive rework in related parts of the solution.
  4. Keep on top of your issues. Many project changes will arise from project issues.


If you are alive about Project Creep in this stage of the Project, you did it! If not, you probably are delayed and you need to close faster than desired.

2 thoughts on “Project Creep”

  1. Scope Creep is actually an Issue rather than a risk. It is something to be managed as part of the project.
    Scope Change Control is the straight forward way. If the customer wants a change, then the Change Control process can deal with it. An assessment of the cost and schedule impact as well the technical impact is done and if the result is acceptable, the project plan is change.
    The notion that agile makes this go away is nonsense. Change occurs in all projects from the smallest to the billion dollar ones. How you manage in the “presence” of this change determines how these changes impact the project.
    All agile does is push the Change Control outside the development process, back to the customer. But ignores the impact analysis as a direct accountability.


Leave a Comment