Project Scope Document

1. Project Scope Document November 1-4, 2011

2. Facts • Creates a common understanding • Prepared by team or team contractor • Has a lot of detail

3. Contents • Usually contains the following sections: • Customer Requirements • Statement of Work (SOW) • Deliverables • Acceptance Criteria • Work Breakdown Structure (WBS)

4. Customer Requirements • Contains 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 specifications • Standards, codes

5. Statement of Work • Contains major tasks or elements • Defines what the team will do • If it is not in here, one should assume it will not be done or provided • States the work scope • See the next slide for an example

6. Example of SOW Project for a community festival: • Prepare promotions- newspaper advertisements, posters, tickets, and so forth. • Solicit volunteers • Organize games, including constructing booths, acquiring prizes. • Contract for amusement rides, and obtain necessary permits • Obtain performers to entertain and workers to construct the grandstand stage. • Arrange for food, including making or purchasing the food and building concession stands • Organize all the support services, such as parking, cleanup, security, and restroom and first aid stations

7. Create a SOW • Choose an activity • Create a SOW for the activity • Bullets are fine, just as the previous example

8. Deliverables • Products or outputs that will be produced or provided at completion of project • A detailed description of each should be provided (helps manage stakeholder expectations) • Creates basis for agreement

9. Acceptance Criteria • Criteria for accepting each deliverable • May 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.

10. Questions • Describe a project scope document. Why is it important to clearly define the scope? • Make up a deliverable. Create a set of acceptance criteria for it.

11. Work Breakdown Structure (WBS) • Major work elements defined • A 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)

12. Creating a WBS • After 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.

13. Responsibility Assignment Matrix (RAM) • Defines who will be responsible for work • Tool used to designate individuals responsible for work items • Shows each person’s role in project • May 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

14. Questions • What is a work breakdown structure? What is a responsibility assignment matrix? How are they related? Complete the case study I passed out.

15. Define Activities • See your packet for this information