Project scope statement
(→Background) |
(→Application) |
||
Line 10: | Line 10: | ||
===Scope Planning=== | ===Scope Planning=== | ||
− | == | + | ==Practical Guidelines== |
== Limitations == | == Limitations == |
Revision as of 19:24, 12 February 2018
Contents |
Abstract
Defining a project scope statement is an essential part of any project. It is a tool used to identify the main deliverables of a project along with the key milestones, the boundaries, assumptions and constraints. This statement of work documents also the responsibilities of each member of the project team and procedures for verifications and approves of completed work. Both the project team and all of the stakeholders have to agree with all of the terms suggested in the scope statement before the actual project work begins. Even though the project scope statement is supposed to head the project into the right direction the situation can change as the project progresses. The changed situation has to be assessed on all aspects of the project and necessary changes have to be proposed to the project scope statement. The scope statement needs to be adjusted if the changes are approved. A well-written scope statement is an important part to achieve a successful project and the four main aspects which a good statement should include are the project justification, the project product, the project deliverables and the project objectives. These aspects will be discussed in more details in the following article. [1]
Background
A brief introduction about what a scope is and about what has to be done before the project scope statement can be initated, the initiation phase and the scope planning.
Initiation
Scope Planning
Practical Guidelines
Limitations
Reference
- ↑ Page 56, 1996 ed. PMBOK® Guide
Bibliography
William R. Duncan (2000), pages 55 - 57: A Guide to The Project Management Body of Knowledge: This guide provides deeper insight into the topic of Project scope statement to give further input into the process of scope statement.