There is a school of thought that argues that, far from being undesirable, some degree of scope creep may in fact be beneficial for certain types of projects e.g. it encourages stakeholder engagement, indicates responsiveness, and shows that objectives and WBS tasks are being regularly re-evaluated and re-aligned. The only caveat is that whatever scope creep occurs is properly managed and controlled.
Do you have any opinions on this view of scope creep?
Project scope creep is an element in the project that is not avoidable. It is because changes can occur at any given time during project execution. Project scope creep is not at all bad, and can also be considered good when the project ...
This posting contains answers to the given questions.