When a project deviates from the original request it causes “scope creep” . If not managed properly, scope creep can push timelines, increase budgets, effect resourcing, and frustrate your team and clients.
But don’t worry, Anderson Direct Marketing has a few tips that treat scope creep and help to ensure a project’s success.
Document
Anderson says, "Don't let scope creep get to you!"
- Have a process by which a project scope is defined, documented, and approved. Usually this is done in a statement of work (SOW) or a contract.
- Get as detailed as you can! Include verbiage in the SOW regarding deliverables, time frames technical needs, approval process, roles and responsibilities, assumptions, risks, management, hosting, as well as the process should changes in scope occur.
- When scope starts to change be sure to write it down. Whether you send it in an email to the team and the client or you amend the original SOW, it’s best to have an archive of all updates to a projects deliverables.
Communicate
- As soon as a deviation in scope occurs, even if it’s a small one, let the client know immediately. This will help to eliminate any surprises.
- Offer solutions. Perhaps the new request can occur with the next release of the project and be deployed in a second phase.
