Scope

Term Definition of Scope

In the field of project management, scope refers to the detailed set of deliverables and/or features for a project. These deliverables are derived from the project’s requirements. The work breakdown structure can be one way of expressing a project scope although generally scope is more clearly defined using scope documents and text that describe exactly what will be delivered.

In most cases, a good scope document explains in detail every deliverable item and specifically mentions exclusions. For example, a project scope can be consist of the detailed deliverables for “building a house”, and specifically mention “landscaping is not included”.

What is a project’s scope?

A project’s scope is the clear identification of the work required to successfully complete or deliver a given project. One of the project manager’s responsibilities is to ensure that only the required work (the scope) will be performed and that each of the deliverables can be completed in the allotted time and within budget.

There is nothing wrong with scope change; it is how scope change requests are managed that can have a detrimental impact on the project. In the early stages of a project, the customer often cannot identify or clearly describe all requirements and objectives. Furthermore, business and market changes may force requirement, specification and scope change.

Project scope control and management is often overlooked in the management ranks. However, the impact of lax scope control on the organization, its customers, and its employees’ careers can be devastating. Scope management is not someone else’s problem; executives have to recognize this threat and establish effective internal controls that deal with this often invisible and consistently underestimated risk.

So now you must answer, is scope change a bad thing?