If you’re a project manager who doesn’t know what scope creep is, then you either don’t have the right knowledge or are very lucky. It happens to everyone, but it is possible. It can start small but escalate to become more than you, your team and timeframe can handle. In practice, scope creep looks like this: The project is running smoothly. All deadlines are met, budget is under control, and everyone is on the same page. Stakeholders suddenly insist that the original scope of the project must be expanded or modified. These requests could range from “develop an additional feature (or two)” to “change app specs”, to “take what’s already been created and refurbish it so that it can be used in a different way.” Unexpected requests may also impact realization. Team, deadlines, budget, and budget were all chosen/determined according to the project scope. All changes, large and small, will eventually result in the final product being identical to the original agreement. There is also a risk of dissatisfaction among the team, delays and budget breaches – all consequences of scope creep.
Scope creep is most often caused by uncertainty. Do you think you can count on the details being sorted out in the future? You shouldn’t… Uncertain project scope is the leading cause of scope creep “emergence”. This is why it is so important to have a detailed project initiation. You can go through the project scope and make adjustments as needed. Once you have answered all your questions, you can move on to the next phase. There is no one to stop them (or just tell NO) and product requirements will continue to pile up until scope creep becomes “something you need to learn to live with”. Either the project manager underestimated the complexity of a project (due incompetence or inexperience) or they are too confident in their teams’ ability to meet unrealistic deadlines. Overpromising will not bring you any benefits, no matter what the reason. What’s more, it will most likely cost you money, time and reputation.Communication bypass – Client doesn’t like you (or the project manager). They do like a member on your team, however. They decide to only talk to one member of your team, leaving you out in the loop. Uncontrolled communication can lead to indecent proposals, shady deals, and ever-expanding client demands that one or more team members are not ready to handle. It requires compromise, and neither of the parties to the conflict is happy with it. The problem comes when you and your team need to reevaluate the project in order to find the middle ground.
Scope creep is the “make everyone happy” order. You will need to create the product with all the bells, whistles, and more. This will not only increase the time and money required to complete the project, but it will also result in a complex product that goes beyond the original project scope.
It is easier (and more cost-effective) than arguing until all stakeholde are satisfied.
