Project Scope Management (PSM)

Source: Wikipedia: Project Scope Management

Additional Resources:

The Scope Statement provides a common understanding of the project among stakeholders. Some organizations create a separate Scope Statement Document while others make it a part of the Project Charter or Project Plan.

* 1 Scope Statement
* 2 Project Scope management
* 3 Problems
* 4 Problem Tackling
* 5 References

[edit] Scope Statement

The preliminary Project Scope Statement specifies what should be the goals and objectives of the project and what needs to be accomplished for the project.

A project scope statement includes the following:

* Project and Product Objectives
* Product Acceptance Criteria
* Project Boundaries
* Assumptions and Constraints
* Project Requirements and Deliverables
* Initial Defined Risk
* Schedule
* Work breakdown structure
* Summary of Budget
* Configuration Management

The preliminary project scope statement can be created on the basis of the information from the client side. The inputs used here are:

* The project charter,
* The project statement of work (SOW)
* The enterprise environmental factor
* The organizational process assets

Project Management Methodology (PMM) helps the project managers in developing and controlling changes to the preliminary project scope statement. The Project Management Information System (PMIS)is an automated system that is used by the project managers,which facilitates:

* creating a preliminary project scope statement
* facilitating feedback
* Document refining
* change control
* release the approved document
* Applying Expert judgment

[edit] Project Scope management

Project Scope Management Managing the agreed work within the stakeholders and managers.

A clear and well defined scope is very important for the completion of any minor or major project on time.

Project Scope Management comprises five processes:

* Scope Planning
* Scope Definition
* Create work break down structure
* Scope Verification
* Scope Control

The Scope Management Plan should be part of the Project Plan.
[edit] Problems

There are two areas that are creating problems and common in nearly any type of project.


In systems projects, it can mean conversion from one system to another. Or from one data format to another. Or of hardcopy files to a digital form.

In business projects, it can mean conversion from one set of procedures to another. Or from one organization to another. Or from one location to another.

A useful way to think about conversions: Anything in a project that needs to be one way one day and another way the next.


In systems projects, it can relate to information required by government agencies Or exchanged between systems within your organization Or involving manual steps in the middle of automated processes.

In business projects, it can relate to processes that involve governmental agencies Or with external business partners Or across lines of business.

A useful way to think about interfaces: Any entity outside of your own, to whom you owe or require information to meet your day to day commitments.
[edit] Problem Tackling

'The best answer is to scope it early.
[edit] References

* Project Scope Management By Sivaraj Dhanasekaran.
* Clarise Z. Doval Santos, PMP, CTO, InterActive Systems & Consulting, Inc.
* Two Common Trouble Spots By Barry Otterholt

Retrieved from ""
Categories: Project management

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License