To begin with, I would like to share a story. A couple of years ago I had a project. We were building an e-commerce marketplace. It was a large project and it lasted over a year.
We had a scope for it. However, the client was very creative and he was always asking for additional features and modifications to the project scope.
What is more, the team was really engaged in the work. They liked the project and they wanted to do it better. Besides, they saw the client’s creativity and; in some moments when they felt they could do things better or easier, they implemented the changes to the project on a flight. Everybody was willing the project to be better than it was originally planned.
Finally, with the common effort we have built this marketplace. But, it was barely similar to the original design.
I’ll tell you. The actions of the team were not appropriate. Specifically, the actions during the moments when they felt creativity.
You might think, what is wrong? People were engaged and motivated; they wanted to do things better; the team knew how to do things better and they did that.
Well, all is totally fine until the moment which says ‘they did that’. The wrong thing is that the intermediate step is missing.
Scope creep could be anything, starting from the new button shape and ending with the complementary feature that someone adds at his/her own discretion.
Is scope creep bad?
Let’s discuss why.
Imagine, you are a customer. You have an idea of the product and a certain budget you are willing to spend on it. You found a team or an agency; together we have discussed the project scope and shook your hands. Now you are expecting to get what you have agreed on in the end.
When the time comes, you are getting the product with some extras implemented that you were not aware of. What is more, you may not even want them to be implemented.
Another negative effect is that the product with those extras could cost more than you were originally willing to pay.
Would you still want to work with that team further?
We can see that scope creep leads to problems with the customer.
Next, it impacts the project scope, budget and in many cases even a timeline. It impacts all the tree general project KPIs.
As a result it puts a shade on your relationships with the client. What is more, you could be considered as a not reliable and not professional manager.
It could be even worse if the scope creep was not caught by the project manager during the scope verification and was addressed by the client as a product error.
Definitely, scope creep is something we do not welcome on projects.
To sum it up, scope creep is something that was implemented on the top of the project scope without approval and that is passing by the change management process.
About the Author:Kristina Kushner is a PMP-certified Project Manager. Having years of experience in Tech leading international and globally distributed teams now she shares her expertise through social media. She leads a blog and the Project Management Sandbox YouTube channel. Passionate about Project Management, these days besides the practice in the field, Kristina helps people to start a career in Tech without knowing how to code. Having a diverse background, she understands how challenging it can be to start a career in tech from scratch and with no guidance. Through being a true STEM ambassador her ambition is to help more people succeed in technology.