The project scope statement is a summary description of the project scope used to maintain alignment between stakeholders and team members.
When to use
The scope statement is often redundant with elements found in the Project Charter. It is most useful when the project team is virtual and there are many different stakeholders with different goals for the projects. The scope statement is used as a regular reminder for team members as to what the project is intended to do, and often what is even more important, what it is not intended to accomplish. When working with a small simple project that has a good Project Charter, I recommend that you just work with the Project Charter and don’t create an additional document.
- Start with the Project Charter and use that to identify the deliverables. Many Project Charters will use the “In-frame/out-of-frame” lists to clarify the scope boundaries.
- If necessary, progressively elaborate the scope to clarify deliverables. The scope statement is writtten at the deliverable level, not the task level. There is no need to deploy the deliverables.
- Create a clear description of acceptance criteria, the definition of done, for each deliverable.
- Coordinate the scope statement with stakeholders.
- Coordinate the scope statement with team members and SMEs.
- Based upon the scope statement, identify areas of project risk with respect to accomplishing all of the scope.
- Periodically review and update the scope statement, I recommend at the beginning of each project phase.
- Scope Statement: “The description of the project scope, major deliverables, assumptions and constraints.” PMBOK® Guide
This definition is taken from the Glossary of the Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017.Login to download
Lesson notes are only available for subscribers.
PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.