Scope creep

Poorly defined project scope Ineffective project management communication between a client and the project manager is a leading effect of project scope creep. An assignment that is not understood correctly will turn out to be completely different from clients vision. With that being said clients can also be to blame as they may not see a clear vision of what they want. Project vagueness or complexity A factor in scope creep is when an unexpected hurdle comes up, and arguments occur on if the scope of work document covers it. When certain documents are either too technical or lack critical details, scope creep can appear through interpreting these documents. As a project is planned to be longer or more complex, instances of scope creep are more likely, which could harm the project. Lack of project management practices Adoptions and adhering to project management practices and project management processes are confirmed methods of preventing scope creep from dismantling the project. Addition of unnecessary features Sometimes project teams tend to start adding additional features in order to impress the client. This may not work and tend to cause more work for such project and throw off the scope. Low cost of change Scope creep can more easily enter projects while presented as small, simple, and easy to implement changes. However, the volume or actual complexity of these changes can risk project failure. One example is when team members suggest adding new features in the client's presence. Scope creep is a risk in most projects. Most megaprojects fall victim to scope creep (see Megaprojects and Risk). Scope creep often results in cost overrun. A "value for free" strategy is difficult to counteract and remains a difficult challenge for even the most experienced project managers. == Common effects ==

Risking the project by altering project foundations Scope is key for defining both the physical facilities and project deliverables, and scope creep changes at least one of them. By affecting at least one, scope creep goes on to affect other parts of the project, such as project timeframe and cost. One part of how scope creep causes project delays is by creating the need for more meetings to discuss new scope parts and make decisions on if they should be implemented. Costs can go up due to these delays and new risks may emerge due to the new additions. When cost gets too high, the project goes on too long, or both, projects can fail and higher-ups may look for alternatives to the project. Useful changes and advantages Scope creep can give a project advantages, such as by creating a better final product from the perspective of the client or making the final product better than similar products from other projects. When scope creep is controlled, it can help the project meet its needs by allowing useful changes through. Scope changes are common in projects more than a week, and that makes managing scope creep key to avoiding its negative effects while getting the benefits of useful changes. == Management techniques ==

Having clear foundational documents It is critical to have documents that clearly define to both the client and project team what the project's scope is, what the goals are, and the methods for changing the scope. If the analysis finds no excessive cost, then its implementation can be proposed. Another strategy that can be implemented when changes are proposed is questioning the suggested change to ensure it is well justified. For changes the client proposes, accepting them solely to please the client risks the project, and those changes could be a part of a follow-up project. Occasionally refusing customer requests is key for project management since it can reduce the risk of scope creep causing project cancelation. ==See also==