Define Scope
Figure 8: Define Scope: Inputs, Tools and Techniques, and Outputs. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), (5th Edition)" by Project Management Institute, 2013, p. 120. Newton Square, PA: Project Management Institute, Inc. Reprinted without permission
Figure 8: Define Scope above depicts all the possible inputs tools and techniques resulting in Project scope statement and Project document updates.
5.3 Define Scope
Process Definition
This process defines the parameters of a project based upon the requirements presented and formulates project constraints. The input of the requirements and delegates are further defined in each scope requirement.
Process Assessment
Scope Management plan when done correctly with the necessary controls and constraints can eliminate scope creep which eliminates budget and cost overruns due to creeping requirements. A change control board deals with scope and requirement change requests in a project and this eliminates scope creep.
Define Scope
5.3.1
Input
PGMT 502, project charter from Paws for Adoption is a high-level summary input of the requirements and delegates responsibilities to who will further define the success of each scope requirement.
5.3.2
Tools and Techniques
This paper makes the case for defining requirements and freezing the product life cycle. This technique prevents additional delays to the project or product. Creeping scope requirement is why projects fail.
5.3.3
Output
In PGMT 611, dealing with the reorganization of the ITD department a detailed output description enumerates the scope its constraints, and assumptions associated with the deliverables.