PMI defines scope creep as “adding features and functionality (project scope) without addressing the effects on time, costs, and resources, or without customer approval” (PMI, 2008, p 440).  Scope creep causes the project to lose definition, and stakeholders may carry unreasonable expectations throughout the entirety of the project.  In my experience, scope creep most often occurs when additional subject matter experts are brought into the project late in the game by the client – and the PM is faced with a litany of, “where is this functionality?”  It is important for the PM to define the scope of the project from day one, and to review it in weekly meetings.  Follow the link below to see what Stephanie Ray has to say about this critical subject:

Before we can explain how to avoid scope creep in…Read More »

The post What Is Scope Creep and How Can I Avoid It? appeared first on ProjectManager.com.
http://dlvr.it/S0VF7C