Project's Scope Change

In project management concept, scope management is directly connected with managing the changes required during the execution of projects, arises from the need for efficient and effective control over projects. Several researches on scope and change management showed the common causes of project's scope change, as follows:

1. Poor scope statement - incomplete and ambiguous scope statement, inconsistent with project assumptions, deliverables does not address the customer required (missing, unnecessary or inaccurate deliverables) will cause project scope changes. 

2. Poor requirements definition - Deliverables are correct, but the project was incorrectly defined in the first place will cause the scope changes. Because the more gaps that you have in your requirements, the more scope changes you are likely to have. Please be noticed that requirements definition and requirements management play important roles on project success. There are several causes of poorly defined requirements, i.e. ineffective or wrong techniques used to gather requirements, communication breakdowns between analyst and stakeholders, requirements are not aligned with project scope, requirements do not address complete process work flow, documented requirements are not meaningful to targeted audience, requirements not reviewed for inconsistencies, requirements not verified for correctness and completeness, missing stakeholders and users sign-off without a "real" understanding of what the documented requirements mean.

3. Customer or stakeholder request - due to the dynamic nature of business world today, things can change quickly. Change in business will cause customer or stakeholder request change to the project. Example of business change that can alter a project's scope include: available budget/funding for the project, new government regulations, changing target market for the product, time-to-market pressures, new business opportunities, changing customer priorities, unexpected market or world events. In order to minimize unnecessary changes in project scope, early in the project, you should define and publish the criteria and the timeline for accepting discretionary project scope changes.

4. Value added change  - For example, a team member may find a better, faster, less expensive way to do the work and still meet the project deliverables.

5. External condition - For example changes in regulatory requirements, changes in the organization's priorities, or changes in the market or technology - are outside of the project's manager control but must still be accommodated.  For instance, there is new technology available during a project that will significantly meet the needs of the customer much better than what is currently planned.