Scope and Work Breakdown Structure

profilearqbogs
cf_scope_statement_template.docx

PM4040 Scope Document

Project Name:

Project Overview

Describe the background and context for the project and why it is being undertaken. Discuss the business value of the work being performed.

Project Scope.

This section is where you clearly define the logical boundaries of your project. These statements are used to define what is within the boundaries of the project and what is outside those boundaries. Data, processes, applications, or business areas are items that could be examined. The following might be helpful to include:

The types of deliverables that are in scope and out of scope (business requirements, current state assessment).

The major life-cycle processes that are in and out of scope (analysis, design, testing).

The types of data that are in and out of scope (financial, sales, employee).

The data sources (or databases) that are in scope and out of scope (billing, general ledger, payroll).

The organizations that are in scope and out of scope (human resources, manufacturing, vendors).

The major functionality that is in scope and out of scope (decision support, data entry, management reporting).

The scope of this project includes and excludes the following items:

In scope:

Out of scope:

Deliverables produced:

All projects have deliverables. In this section, describe the deliverables of the project. Provide enough explanation and detail that the reader will be able to understand what is being produced. Make sure that the deliverables produced align with what is in scope from the previous section.

Deliverable 1: <deliverable description>

Deliverable 2: <deliverable description>

Deliverable 3: <deliverable description>

Critical Success Factors

.

.

Assumptions

.

.

1

Capella Proprietary and Confidential