Addition of one more requirement or one more feature overall “Scope Creep” is one of the biggest causes of IT Project failure. If scope is well managed then it can be an up-selling, resulting in more revenue for vendor and joy for customer. On the other hand, if unmanaged it becomes a statistic and topic for this post.
How is scope creep introduced?
- Scope is not properly defined.
- Not giving sufficient time for requirement definition. More complex the business requirement, more thorough analysis and time for that analysis is required. In fact, in such situations Agile Project Management can be most suitable.
- Not involving all the required stakeholders at appropriate time. The stakeholders can be a customer or development function.
- Change in business or technical landscape.
- Perfectionist developer (Gold plating) or customer associate
- More leeway to customer and thus customer expects that a little more than what is committed / paid for is acceptable.
How can you reduce/control scope creep?
- Scope must be very well defined and documented. Every project stakeholder must be aware of the scope. Project development team should be the champion of project scope.
- Instill “investigate and then confirm” in project team. No one should say yes to any minor requirement unless that is documented in scope.
- Start investigation at the hint of it.
- If an item is out of scope then state to customer that that is out of scope.
- Associate a price tag to every new requirement.
- All changes must go through change control mechanism – change control board, change manager, change management form.
- Conduct sufficient requirement analysis and communicate with customer about the progress of the solution. A complex project requires more analysis. Breaking the solution into short stints as in Agile may be helpful.
- Involve all stakeholders until the requirements transform into business solution (A-Z). There must be a very good reason to not include a stakeholder.
- Present prototypes and mock ups to facilitate customer in defining requirements. Keeping customer abreast of the development and communicating with customer when there is any doubt can be helpful. However, changes in requirement should still be seen with a grain of salt.
- Define project risks and mitigation plans thoroughly especially that affect scope, cost or quality.
- Keep buffer in project plan to investigate and manage scope creeps.
Do you face scope creep in your projects? Do you use any other technique to manage scope creeps?