November 1-4, 2011

Project Scope Document

FactsCreates a common understanding Prepared by team or team contractorHas a lot of detail

ContentsUsually contains the following sections:

Customer RequirementsStatement of Work (SOW)DeliverablesAcceptance CriteriaWork Breakdown Structure (WBS)

Customer RequirementsContains specifications and requirements

(ex. Colors, size, weight, speed, temperature, etc)

NOW, right down ONE example of your own in your notes

Should include if applicable:Technical specificationsStandards, codes

Statement of WorkContains major tasks or elementsDefines what the team will doIf it is not in here, one should assume it will

not be done or providedStates the work scopeSee the next slide for an example

Example of SOWProject for a community festival:Prepare promotions- newspaper advertisements,

posters, tickets, and so forth. Solicit volunteersOrganize games, including constructing booths,

acquiring prizes.Contract for amusement rides, and obtain

necessary permitsObtain performers to entertain and workers to

construct the grandstand stage.Arrange for food, including making or purchasing

the food and building concession standsOrganize all the support services, such as parking,

cleanup, security, and restroom and first aid stations

Create a SOWChoose an activityCreate a SOW for the activityBullets are fine, just as the previous

example

DeliverablesProducts or outputs that will be produced

or provided at completion of projectA detailed description of each should be

provided (helps manage stakeholder expectations)

Creates basis for agreement

Acceptance CriteriaCriteria for accepting each deliverableMay contain standards, codes,

measurements, may involved quality. Other examples include sampling, test procedures, testing length, lab procedures, etc.

Must be clear. Basis for verifying scope meets customer’s expectations.

Questions1. Describe a project scope document. Why

is it important to clearly define the scope?2. Make up a deliverable. Create a set of

acceptance criteria for it.

Work Breakdown Structure (WBS)Major work elements definedA technique for organizing and subdividing

all work and deliverables into manageable portions

WBS establishes for further planning to create baseline for the project and HOW the work will get done.

Used as basis for creating a more detailed WBS in the next steps of the planning process (you will work off of this)

Creating a WBSAfter project scope document has been

prepared and agreed upon, create the WBS.

Lowest level work item is called a “work package”. Includes all specific work activities that need to be done to make the deliverable

Create using a graphic chart or as an indentured list. See document camera for examples for both formats.

Responsibility Assignment Matrix (RAM)

Defines who will be responsible for workTool used to designate individuals

responsible for work itemsShows each person’s role in projectMay use a “P” to designate primary

responsibility and an “S” to indicate support.

Only one person can have primary responsibility- confusion happens if two are listed

QuestionsWhat is a work breakdown structure? What

is a responsibility assignment matrix? How are they related?

Complete the case study I passed out.

Define ActivitiesSee your packet for this information