Card Set Information
Knowledge area with 5 processes that are concerned with gathering requirements, documenting the scope, breaking it down, verifying that it was performed completely, and controlling changes.
1. Collect Requirements (planning)
2. Define Scope (planning)
3. Create WBS (planning)
4. Verify Scope (M&C)
5. Control Scope (M&C)
Planning process within Scope Management where product requirements are gathered and documented. Usually performed early in the project or phase and may be revisited.
Requirements Traceability Matrix
Planning process within scope management that produces the project scope statement.
Project Scope Statement
Planning process within Scope Management where the work
breakdown structure is created and the scope is baselined.
Monitoring & Controlling process within Scope Management where there deliverables are compared against the documented scope.
Monitoring and controlling process within scope management where change requests are managed and changes to the scope baseline are detected.
Work Performance Information
Group Creativity Techniques
A tool used in the process of Collect Requirements. It includes:
- Nominal Group Technique
- Delphi Technique
- Idea and Mind Mapping
One of 3 baselines in the Project Plan (along with the schedule baseline and the cost performance baseline). The scope baseline is made up of the following:
- Scope Statement
- WBS Dictionary
Delivering features or functionality that are not documented in the project's scope. Gold Plating is considered to be bad because extra functionality increases risk since it was outside the plan.
(Work Breakdown Structure)
A chart that represents all of the work to be performed on the project.
- Comprised of boxes called nodes
- Lowest level of nodes are called "work packages"
- Represents all of the work to be done on the project
Project Scope Statement
The detailed description of the project's products or services. The Scope Statement is used to foster a common understanding among stakeholders. It includes a description of:
- Acceptance Criteria
The relationship between scope time, and cost. The triple constraint indicates that if scope, time, or cost changes, at least one of the other two will be affected.
Also known as the iron triangle:
TIME - COST - SCOPE
The lowest level of nodes on the WBS. Work packages have the following characteristics:
- Represent all of the work to be performed on the project
- Consists of roughly 1 day to 2 weeks in duration
- Small enough to be estimateable for the cost & time
- May be assigned to a single person or entity