Scope statement

Scope statements can take many forms depending on the type of project being implemented and the nature of the organization. The scope statement details the project deliverables and describes the major objectives. The objectives should include measurable success criteria for the project.

Overview

A scope statement should be written before the statement of work and it should capture, in very broad terms, the product of the project (e.g., "developing a software based system to capture and track orders for software"). A scope statement should also include the list of users using the product, as well as the features in the resulting product.[1]

Contents

As a baseline scope statements should contain:

In more project oriented organizations the scope statement could also contain these and other sections:

  • Project scope management plan
  • Approved change requests
  • Project assumptions and risks
  • Project acceptance criteria

The Project Management Institute (PMI) defines the project scope statement to include

  • the description of the project scope,
  • major deliverables,
  • assumptions, and
  • constraints.

and is part of the project scope baseline.[2]

gollark: Java = EVIL
gollark: No idea how good support for, well, anything is.
gollark: There's a Python thing for OC.
gollark: One does not "figure out" openCOMPuters.
gollark: I kind of like it, it's good for it to be able to handle high radiation environments better.

References
  1. Nielsen, David (date unknown). How to Write the Project Statement of Work (SOW). Retrieved on 2010-03-22 from http://www.pmhut.com/how-to-write-the-project-statement-of-work-sow.
  2. A Guide to the Project Management Body of Knowledge, 5th Edition ISBN 978-1935589679, p. 131.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.