Scope Management

Define

scope refer to features and functions that are to be included and what are not to be included

the project must have specific features and functions according to demand

include all the work required to complete the project

outline and boundaries of a project

Features

concise

anyone reading the statement should get good idea of about what the project/system is.

to be specific

give clear brief view of project

includes team name, start and end date,objectives,cost estimation etc.

Example

The catalog featuring 100 products" is better than "The catalog featuring many products" and "The project will be completed over six months" is preferable to "The project will be completed over a period of time."

The more specific you can be, the better.

justification

scope description

requiement

deliverability

cost estimation

finalisation and acceptance

Justification

Simply identifying the reason for the project's existence.

It is usually a statement or two identifying why the project is being created.

It’s important to have the project justification identified because achieving the final goal.

The project justification should be in clear and precise manner so that it identifies a measure of success

Scope Description

list of applications

buisiness processes

Requirement

The requirements are objectives that must be met during the project.

They include significant milestones or goals.

The objectives need to be quantifiable and identified clearly.

also include technical requirement like security,avaibility

DeriverabilityNeed to be clearly identified within a scope statement.

A final product to be provided to the stakeholders.

No matter what makes up a project's deliverables, specific details regarding them is the golden rule.

The more clearly the deliverables are identified and specified, the less chance there will be for scope creep to occur later on.

Cost EstimationThis is an essential process of project planning, so the cost estimates should be as accurate as possible.

If the cost estimates are too low, the project will go over budget.

If the cost estimates are too high, resources that are allocated to the project - whether they are money, equipment or people - are unavailable for other projects and could negatively affect them.

So the more on track the cost estimates are, the more efficient and successful the project will be. This can be a difficult task for the project manager to do, but effective cost management is a critical success factor for projects.

Finalisation and Acceptance

Once the project manager has scope statement, all of the major stakeholders as well as the project owner need to sign off on it.

This is a very significant step . At that time, any discrepancies can be cleared up or last minute changes can be made.

By having everyone sign the scope statement, there is very little chance of surprises down the road. And in the event that something does pop up, there is documentation of what was agreed upon initially so that changes can be made if necessary. If anything does change down the road and the scope does need to be increased for some reason, signatures should be obtained from everyone once more.

Conclusion

Exhaustively detailed specifics, clear and concise language throughout, and avoiding ambiguity are the keys to making a scope statement effective and useful.

It is also very beneficial to have all of this information documented in one place - even if the process of creating it is enormous.