PROJECT SCOPE STATEMENT

Put your logo herePut your organization name hereProject Scope Statement Template

Prepared by Project Management Competency Center, PMI - REP

Rev. 2.0, 12/01/2004

PROJECT SCOPE STATEMENTNote: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project. It is a Project Management Team document.

Create links to referenced documents (e.g., Link _ To _ Project Charter _ Contract _ Preliminary Project Scope Statement) by using Insert ( Hyperlink on your toolbar.

Note that all documents that are linked to the Project Scope Statement become part of the Project Scope and require the same degree of management control. Such documents should be maintained in a separate Scope directory along with the Project Scope Statement.

Project Name:

Prepared by:(Name of the Project Manager of the Project)

Date (MM/DD/YYYY):

Version History (insert rows as needed):

VersionDate(MM/DD/YYYY)Comments

1.0

1. Business Objectives

1.1 Executive Summary:

Link _ To _ Project Charter

1.2 Business Objectives:

Link _ To _ Project Charter _ Project Feasibility Report

1.3 Product Description (Solution):Link _ To _ Project Charter

Note: In any instance where there is a discrepancy between the Project Charter and the Project Scope Statement, the latter is considered authoritative. It provides the baseline for evaluating whether request for changes or additional work are contained within or outside the project boundaries.

2. Project Objectives

2.1 Product Description (Solution):Link _ To _ Preliminary Project Scope Statement _ Contract

>

2.2Project Objectives:Link _ To _ Preliminary Project Scope Statement _ Contract

>

Information in the Project Objectives must include Targets and attributes such as metrics and an absolute and relative value (Rupees, US $, Milestone dates etc.)

2.2.1Cost Objectives:Link _ To _ Preliminary Project Scope Statement _ Contract

2.2.2Schedule Objectives: Key project milestones relative to project start are: (Insert rows as needed):

Project MilestoneTarget Date (MM/DD/YYYY)

Project Start

Project Complete: Link _ To _ Preliminary Project Scope Statement _ Contract

2.2.3Technical Objectives:Link _ To _ Preliminary Project Scope Statement _ Contract

2.2.4Quality Objectives:Link _ To _ Preliminary Project Scope Statement _ Contract

3. Product Scope Description

For each area below, provide sufficient detail to define adequately the characteristics of the product, services or results that the project is undertaken. The characteristics provided here might have less detail in early phases and more detail in later phases as the product characteristics are progressively elaborated.

3.1 Product, Service, or Result Scope: Link _ To _ Preliminary Project Scope Statement _ Contract

List of Final deliverables included:

Prepare Product Breakdown Structure (PBS) to ensure the completeness of the product scope before listing the final deliverables.

>

Deliverables Not Include:

>

3.2 Product Acceptance Criteria:Link _ To _ Preliminary Project Scope Statement _ Contract

>

3.3 External Dependencies:Link _ To _ Preliminary Project Scope Statement _ Contract

>

3.4 Assumptions:Link _ To _ Preliminary Project Scope Statement _ Contract

3.5 Constraints:Link _ To _ Preliminary Project Scope Statement _ Contract

>

4. Project Requirements, Deliverables, and Project Boundaries

4.1.1 Requirement Phase: List major Intermediate Deliverables Link _ To _ Preliminary Project Scope Statement

>

>

>

>

4.1.2 Design Phase: List major Intermediate Deliverables Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

4.1.3 Construct Phase: List major Intermediate Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

4.1.4 Test & Installation Phase: List major Intermediate Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

Does Not Include:

>

4.2.1 Requirement Phase: List major Organizational Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

4.2.2 Design Phase: List major Organizational Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

4.2.3 Construct Phase: List major Intermediate Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

4.2.4 Test & Installation Phase: List major Intermediate Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

>

>

>

>

Does Not Include:

>

4.1.1 Project Management Phase: List major Project Management Deliverables: Link _ To _ Preliminary Project Scope Statement _ Contract

4.1.1.1 Project Initiation Process Group: (List major Project Management Deliverables in the Initiation process group)

>

>

>

>

Does Not Include:

>

4.1.1.2 Project Planning Process Group: (List major Project Management Deliverables in the Planning process group)

>

>

>

>

Does Not Include:

>

4.1.1.3 Project Execution Process Group: (List major Project Management Deliverables in the Execution process group)

>

>

>

>

Does Not Include:

>

4.1.1.4 Project Control Process Group: (List major Project Management Deliverables in the Control process group)

>

>

>

>

Does Not Include:

>

4.1.1.5 Project Closing Process Group: (List major Project Management Deliverables in the Controlling process group)

>

>

>

>

Does Not Include:

>

5. Project Acceptance Criteria

5.1Define the process and RAM for accepting completed products, service, or results:Link _ To _ Preliminary Project Scope Statement _ Contract

>

5.2Define the acceptance criteria for completed deliverables of products, service, or results:Link _ To _ Preliminary Project Scope Statement _ Contract

6. Project Constraints, Assumptions, & Initial Project Organization

6.1List Project Constraints: Link _ To _ Preliminary Project Scope Statement _ Contract

6.1.1 List the constraints in meeting the milestones

6.1.2 List the constraints in meeting the Budget

6.1.3 List the constraints in meeting the Quality Requirements

6.2List Project Assumptions: Link _ To _ Preliminary Project Scope Statement _ Contract

6.3List names of key Project Team Members:

6.3.1 List names of key stakeholders in the originating & performing organizations

6.3.2 List names of key team members in the performing organization

6.3.3 List the name of key staff members requirements

6.3.4 Prepare initial Responsibility Assigned Matrix (RAM)

6.3.4 Finalize the project management teams responsibility

6.3.5 Finalize the authority levels of project manager, and project team members

7. Project Identified Risks

7.1List Project Identified risks: Link _ To _ Project Risk Management Plan, Risk Register

8. Project Management

8.1 Primary Plans - will the project have formal written plans i.e., project schedule, budget, quality, risk, etc.? Describe briefly in the space below: Link _ To _ Preliminary Project Scope Statement

8.2 Scheduled Status Meetings (Insert rows as needed):

MeetingPurposeFrequency

8.3 Scheduled Status Reports (Insert rows as needed):

ReportPurposeFrequency

Briefly describe how each of the following will be handled. Provide links to relevant documents as appropriate. Modify example text provided or enter your own.

8.4 Issue Management: Project-related issues will be tracked, prioritized, assigned, resolved, and communicated in accordance with the Project Management Methodology.

Issues will be reported using an Issue Report Form. Issue descriptions, owners, resolution and status will be maintained in an Issues Log in a standard format.

Issues will be addressed with the project owner and communicated in the project weekly status report.

8.5 Change Management:The change control procedures as documented in the Change Management Plan will be consistent with the Project Management Methodology and consist of the following processes:

A Change Request Log will be established by the Project Manager to track all changes associated with the project effort.

All Change Requests submitted via Change Request Form will be assessed to determine possible alternatives and costs.

Change Requests will be reviewed and approved by the project owner.

The effects of approved Change Requests on the scope and schedule of the project will be reflected in updates to the Project Plan.

The Change Request Log will be updated to reflect current status of Change Requests.

8.6 Communication Management:The following strategies have been established to promote effective communication within and about this project. Specific Communication policies will be documented in the Communication Plan.

The Project Manager will present project status to the project Sponsors on a weekly basis; however, ad hoc meetings will be established at the Project Managers discretion as issues or change control items arise.

The Project Manager will provide a written status report to the project Sponsors on a monthly basis and distribute the Project Team meeting minutes.

The project Sponsors will be notified via e-mail of all urgent issues. Issue notification will include time constraints, and impacts, which will identify the urgency of the request for service.

The Project Team will have weekly update/status meetings to review completed tasks and determine current work priorities. Minutes will be produced from all meetings.

All project stakeholders will maintain all electronic Project Documents in central storage accessible.

8.7 Procurement Management:The project team will write a Procurement Management Plan. It will document the following:

How much, when and by what means each of the goods and services that this project requires will be obtained

The types of contracts required (if any)

How independent estimates (as evaluation criteria) will be obtained

Who will actually work to procure any item or service

Which procurement documents will be used

How procurement will be coordinated with project schedule and budget

What a Statement of Work includes (e.g., how to describe a product or service so that a prospective seller can decide if they can supply it)

A description of RFI, RFP, and other processes (if required for the project)

Potential sources of goods and services.

8.8 Resource Management:The project team will produce a Resource Management Plan that will document the following:

Lists all major goods and services required in the project along with cost estimates and quality information.

Indicates which goods and services will be obtained from sources outside the Organization

Indicates who is assigned to the project and when.

9. Authorizations

The Scope Statement, WBS, Project Schedule, Risk Management Plan and Project Budget are approved by the:

Project Sponsor

Project Manager

Project performance baseline changes will be approved by the:

Project Sponsor

Project Manager

Project deliverables will be approved/accepted by the:

Project Sponsor

Key Stakeholders

Specific task responsibilities of project resources will be defined in the Responsibility Assignment Matrix.

10. Project Scope Statement Approval / Signatures

Project Name:

Project Manager:

The purpose of this document is to provide a vehicle for documenting the initial planning efforts for the project. It is used to reach a satisfactory level of mutual agreement between the Project Manager and the Project Sponsors and Owners with respect to the objectives and scope of the project before significant resources are committed and expenses incurred.

I have reviewed the information contained in this Project Scope Statement and agree:

NameRoleSignatureDate

(MM/DD/YYYY)

The signatures above indicate an understanding of the purpose and content of this document by those signing it. By signing this document, they agree to this as the formal Project Scope Statement document.Put your organization name herePage 10