Scope Creep - a Web Developer's worst nigthmare
As web developers, we’ve all been there – working on a project where the client continually makes small and ad-hoc changes requests. Things like "can we change this little thing" or "we would like to have this feature". On the surface, these change requests seem insignificant, so you end up accepting them just to keep the client happy. But eventually they become numerous enough that they turn into something bigger and require much more work than expected. In the end, you find yourself in a situation were you’re doing work that wasn’t defined, resourced and costed in the web development proposal.
Bottom line – you’re doing more work for no extra money. Ouch!
Welcome to the world of scope creep – a web developer’s worst nightmare.
In essence, scope creep refers to the change in a project's scope after the project work has started. It’s most commonly the result of not properly identifying the features that are required to bring about the achievement of project objectives in the first place.
What is Project Scope?
You see, every web project is 1) executed with a set of deliverables and 2) has an expected end date. These deliverables are defined in the specifications section of your web development proposal as features and functionality that need to be developed in order to deliver a successful solution. These features and functionality constitute the scope of a project.
Scope Creep – Get a Grip
Controlling the scope of your project begins before the first line of code is written. This is where a web development proposal can make or break you. By clearly defining the project requirements (i.e. the client’s objectives that must be met) and the project specifications (how you are going to meet those objectives), you dictate, define and clarify the whole scope of the web design and development that you are proposing.
Guidelines for Managing Scope Creep
- Be sure you thoroughly understand the client’s goals and document this in the project overview of the web development proposal. This will give the client a good indication if you’re on the same page or not (so to speak). How to Impress the Client in your Project Overview.
- Define the project specifications by providing general descriptions of the features and functionality to be completed during the project. These can be detailed as functional specifications, technical specifications, design specifications, software add-ons, website component. Whatever! You're basically telling the client "Hey dude, this is what I'm going to develop and deliver as part of the solution."...btw, don't call your client dude...;)
- Break the web project down into project lifecycle phases such as development, testing, implementation and handover and give each phase generous time to complete. Most of your work will be done in the development phase, so give yourself ample time here...and remember, when determining each phase duration, leave room for error.
- Expect that there will be scope creep. Use Work Order forms for change requests outside of the project scope and also educate the client on your processes. You need to make them aware that if a request was not defined in the web development proposal, then it's considered new and additional work which will incur additional costs. A Work Order form will allow you to perform a cost-benefit analysis before tackling such change requests.
If you follow the above steps, then you’ve got a great chance at containing the scope creep monster.
At the end of the day, you need to control your project, instead of your project controlling you.
Tina Pixon
