Question

1. What is Scope creep? Give at least one example from your experience and/or from a article that you have read.

I need really examples

Answer 1

Scope is the documented work plan and deliverables of a project. It details a project’s specifications, schedules, boundaries, and key deliverables. Every project has a scope, i.e. the project’s requirements.The definition of scope creep is when a project’s scope changes, the project work starts to extend, or “creep”, beyond what was originally agreed.

With just about any project, change is inevitable, but it’s the uncontrolled changes that delay projects and cause scope creep. Requested changes that are documented and implemented as part of the updated scope of a project are controlled.The problem comes with any unauthorized changes which can affect productivity, deliverables not being achieved, budgets being exceeded. The completed project can potentially look very different from what was originally envisioned.

SCOPE CREEP EXAMPLES

• Lack of change control: An example of lack of change control would be if you are carrying out a project centred around designing a new product and your client has changes they wish to make to their requirements, neither you as the project manager or your project team would know how to deal with the change needed or where to start in terms of implementing it into the project plan.
• Not understanding how project objectives will be met: If you are involved in a marketing campaign project, for example, and you fail to plan carefully the various tasks that need to be completed as part of the project, then when you begin working on the project these unplanned for tasks will pop up and throw the course of your project off.
• Poor communication: If you are completing program development for a client and you fail to communicate effectively with them throughout the course of the project, what could result is various misinterpretations of what is required and a program that is unsuitable to their requests. Dealing with scope creep in this example could prove very difficult. Always keep communication lines open and consistent with clients and stakeholders.
• Not saying no: If you are completing a project for a client that has a lot of requests and changes to the project that you know are impossible and you still say yes to all of them as the project manager, you are causing scope creep. You need to be able to say no when you understand that something is not possible Try sitting down and explaining to your client why something cannot be changed or implemented, and they are likely to understand.