“Change on projects is inevitable, so the possibility for
scope creep is also inevitable” (Larson, 2009).
During a recent project, my client asked me to create a digital application that will allow users to submit a lease application via her website. The SOW included the only the design and development of the digital application. She later discovered she needed more features and components added to the digital application. For example, she wanted to add an automated workflow that would allow her to approve/deny an application directly from her email. Then, she stated that upon approval of the application, she wanted the system to automatically send the lease agreement to approved applicants. Although the project was delivered on time, the budget was affected by the scope creep. I informed her of the additional cost and the SOW was updated to include the additional features.
In my
experience, clients often do not know what they fully want or need until they do.
This will lead to scope creeps. “Whether scope is initially unclear or it stays
vague as a project unfolds, if the product scope and its underlying
requirements are not clear and precise, it is a “breeding ground” for scope
creep” (Larson, 2009). When we started this project, the client knew she
wanted a digital application included on her website. During the testing phase,
she realized she needed additional features and components. As a project
manager, I am accustomed to scope creeps.
Sources
Larson, R. & Larson, E. (2009). Top five causes of scope creep ... and what to do about them. Paper presented at PMI® Global Congress 2009—North America, Orlando, FL. Newtown Square, PA: Project Management Institute.
A great blog post indeed lack of effective project management communication between the project manager and the clients is usually the biggest hurdle in scope creep risk mitigation. What I have learned is that, when a project manager does not understand the requirements clearly, especially when a client does not give that clarity, the final product will be entirely different from the client’s vision. In most cases, clients are also to blame, especially for creative projects. They often do not have a clear scope of what they want, which leads to more confusion. Statements like “I’ll know when I see it” are a headache for project collaboration between teams. But all after all we can’t avoid scope creep completely and, in some cases, a small deviation from the original plan is necessary for the success of the project.
ReplyDeleteMelanie, you provided a great example of how and why scope creep can occur. In your scenario, the scope creep was justifiable in helping to ensure that the client's needs were met. Not only were you able to accommodate the modification of the SOW and deliver the project on time (kudos!), but you expanded the project to support the client's production. Although more costly, the client's ROI was feasible and of benefit to her consumers making your scenario an example of how scope creep can sometime be a good thing (Resource Management, 2010).
ReplyDeleteReference
Resource Management. (2010, April 23). Can scope creep be a good thing? BrightHub Project Management. Retrieved August 14, 2022, from https://www.brighthubpm.com/resource-management/69354-is-scope-creep-an-asset/#:~:text=To%20begin%20with%2C%20customers%20benefit,sunk%20cost%20of%20a%20project.
Very simple, technical, and to the point . I love it!
ReplyDelete