The scope statement is a detailed description of the project outcomes, including the deliverables, constraints, schedule milestones, risks, and project assumptions. The PMBOK states that this process of describing the project, product or service. It will fine tune the Collection Requirements process to directly relate to the scope of the project.
The scope statement and the WBS work together. A well defined scope statement is required to adequately develop a quality WBS. It is too easy to get derailed, especially in the beginning of a project. This process should take time and be thorough.
Define Scope: Inputs, Tools and Techniques, and Outputs. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide) 5th ed." by Project Management Institute, 2013, pg. 120. Copyright 2013 by PMI.Inc. Reprinted without permission.
1. Organizational Process Assets (Input): Taken from PMGT 612; this artifact was a template that was utilized to define the scope of an outsourced project.
2. Project Scope Statement (Output): This was taken from Group 3 project in PMGT 501. The artifact sheds light on a quality scope statement.
3. Facilitated Workshop (Tools and Techniques): an essay that explains stakeholders roles in facilitated workshops. The example used was taken from an aircraft maintenance unit stand-up meeting.