Scope Management
Defines, validates, and controls what is and is not included in the project.
established project management guidelines definition
Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Scope management is primarily concerned with defining and controlling what is and is not included in the project. The work products include a scope statement, a Work Breakdown Structure (WBS), formal requirements documentation, and a scope baseline against which deliverable acceptance is measured.
Processes in this Knowledge Area
Plan Scope Management
Inputs: charter, PM plan. Outputs: scope management plan, requirements management plan.
No AI_PM requirements primarily mapped to this process.
Collect Requirements
Inputs: charter, stakeholder register. Outputs: requirements documentation, requirements traceability matrix.
REQ-FUN-003— Store requirements with id, project_id, kind, description, acceptance_criteria, status, source_objective
Define Scope
Inputs: charter, requirements docs. Outputs: project scope statement.
No AI_PM requirements primarily mapped to this process.
Create WBS
Inputs: scope statement, requirements docs. Outputs: scope baseline (WBS + WBS dictionary + scope statement).
REQ-FUN-002— Store deliverables with id, project_id, name, description, status, accountable_role
Validate Scope
Inputs: PM plan, verified deliverables. Outputs: accepted deliverables, change requests.
No AI_PM requirements primarily mapped to this process.
Control Scope
Inputs: PM plan, work performance data. Outputs: work performance information, change requests, scope baseline updates.
No AI_PM requirements primarily mapped to this process.
Secondary support
Requirements whose primary KA is elsewhere, but which also support Scope Management.
| ID | Description | Primary KA |
|---|---|---|
| REQ-BUS-001 | System replaces ad-hoc flat-file project state for sponsor-portfolio projects | Integration Management |
| REQ-FUN-013 | Store attachments with id, parent_kind, parent_id, filename, content_hash, storage_uri | Integration Management |
| REQ-FUN-023 | Actor can mark a claimed item completed | Communications Management |
| REQ-FUN-081 | Actor can instantiate a template into a working artifact attached to a project | Integration Management |
| REQ-FUN-090 | Requirement created in AIPM appears (or referenceable) in MAS within 1 minute | Integration Management |
| REQ-NFR-050 | AIPM does not introduce parallel canonical store for data already canonical in MAS | Integration Management |
| REQ-NFR-062 | All scope changes flow through the change control plan | Integration Management |
All requirements primarily mapped to Scope Management (4)
| ID | Description | Primary Process Group |
|---|---|---|
| REQ-FUN-002 | Store deliverables with id, project_id, name, description, status, accountable_role | Planning |
| REQ-FUN-003 | Store requirements with id, project_id, kind, description, acceptance_criteria, status, source_objective | Planning |
| REQ-FUN-129 | Requirements Traceability Matrix view | Planning |
| REQ-FUN-130 | WBS Dictionary fields on deliverable | Planning |