I believe is aware that to avoid scope creep we must have a change control board in place but my question is how to mitigate a scope creep even taking in consideration that a well established Change Control Board is in place, what be the best practices as per your experience a PM shoud adopt to mitigate it ? Saving Changes...
Sort By:
saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
In my opinion tools and authority to use those tools to make change can avoid scope creep.
Like for e.g: A configuration management tool integrated with change management tool will make team to adopt a process to make a change. Therefore anyone who want to make a change has to first go to config mgmt tool and having control over these tools will make sure who is authorized to use it. thus possible scope creep can be mitigated. Saving Changes...
arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
For a specific project, the best way for me to manage scope creek is you need to make sure that the Business Owner is aware and will approve what goes into the backlog. The Business Owner would need to know also the project impacts if the changes are included in terms of cost, time, etc.
Saving Changes...
Michael AdamsSolutions Architect| LANLLos Alamos, Nm, United States
Scope creep is a natural occurance in human relations. People work together, and they begin to talk. During a conversation, someone says, "Wouldn't it work better if we added this enhancement, or altered this functionality?" Someone else says, "Yes, and that would be easy, I'll look into that after lunch." There you have scope creep on a small scale, but if you add hundreds of those together, you get major creep.
Top avoid that, a PM ought to anticipate these sorts of conversations, and maintain a list of proposed changes/enhancements. That way, staff, stakeholders, etc. have a place to record their ideas. Beyond that, the PM has to stress the importance of not enhancing the project now, but rather recording the ideas (maybe for a future release/change).
Revisit the issue briefly, but often. We aren't making changes to this project, but please record enhancement ideas in the enhancement log. Saving Changes...
