3.02 Understanding Project Scope Statement Review Activity

Facilitated Workshops

Requirements workshops are focused sessions that bring key cross-functional stakeholders together to define product requirements.

constraints

Restrictions that limit what you can achieve, how and when you can achieve it, and how much achieving it can cost

Assumptions

Statements about how you will address uncertain information as you conceive, plan, and perform your project.

Project Exclusions

Statements about what the project will not accomplish or produce.

Product Scope Description

The characteristics of the products, services, and/or results and/our project will produce.

Project Charter

The project charter provides the HIGH LEVEL project description and product characteristics.

Project Scope Statement

The project scope statement describes, in detail, the project's deliverables and the work required to create those deliverables. The project scope statement also provides a common understanding of the project scope among project stakeholders.

Deliverables

the products, services, and/or results your project will produce (also referred to as objectives).

Justification

A brief statement regarding the business need your project addressed. (A more detailed discussion of the justification for the project appears in the project charter.)

Acceptance Criteria

A set of conditions that is required to be met before deliverables are accepted.

Expert Judgement

Is used to analyze the information needed to develop the project scope statement. Such judgement and expertise is applied to any technical details. Such expertise is provided by any group or individual with specialized knowledge or training, and is available from many sources.

Project assumptions

Lists and describes the specific project assumptions associated with the project scope and the potential impact of those assumptions if they prove to be false. Project teams frequently identify, document, and validate assumptions as part of their planning process.

Project constraints

Lists and describes the specific project constraints associated with the project scope that limits the team's options. For example, a predefined budget or any imposed dates or schedule milestones that are issued by the customer or organization. When a project is performed under contact, contractual provisions will generally be constraints.

Organizational Process Assets

Policies, procedures, and templates for a project scope statement.

Product scope description

Progressive elaborates the characteristic of the product, service, or result described in the project charter and requirements documentation.

Product acceptance criteria

Defines the process and criteria for accepting completed products, services, or results.

Project deliverables

Deliverables include both the outputs that comprise the product or service of the project, as well as ancillary results, such as project management reports and documentation. The deliverables may be described at a summary level or in great detail.

Requirements Documentation

Describes how individual requirements meet the business need for the project.

Product Analysis

For projects that have a product as a deliverable, as opposed to a service or result, product analysis can be an effective tool. Each application area has one or more generally accepted methods for translating high-level product descriptions into tangible deliverables.

Project exclusions

Generally identifies what is excluded as from the project. Explicitly stating what is out of scope for the project helps to manage stakeholders' expectations.

Alternatives Identification

Identifying alternatives is a technique used to generate different approaches to execute and perform the work of the project. A variety of general management techniques can be used such as brainstorming, lateral thinking, pairwise comparisons, etc.