established project management guidelines Coverage Audit
As of 2026-05-11 (post-approval refresh) - reproducible from doc/help/_data/project-management-guidelines_coverage.json. This audit classifies each of the 49 established project management guidelines processes by how well the 155 AI_PM requirements cover its outputs. Process-level Partial means at least one established_guidelines_mandated output is missing (a Gap at the output level). Subsidiary plans in doc/project-management-guidelines/ are noted where the project handles a process through governance documentation rather than a software feature.
Totals
43Covered processes
2Partial processes
4Out-of-Scope (intentional)
0Output-level Gaps
49established project management guidelines processes
KA × Process Group matrix
Each cell shows the process(es) in that KA / Process Group. Color: green = Covered, blue = Partial (at least one output missing), amber = Out-of-Scope (intentionally excluded).
| Knowledge Area | Initiating | Planning | Executing | Monitoring & Controlling | Closing |
|---|---|---|---|---|---|
| Integration | Develop Project Charter | Develop Project Management Plan | Direct and Manage Project WorkManage Project Knowledge | Monitor and Control Project WorkPerform Integrated Change Control | Close Project or Phase |
| Scope | - | Plan Scope ManagementCollect RequirementsDefine ScopeCreate WBS | - | Validate ScopeControl Scope | - |
| Schedule | - | Plan Schedule ManagementDefine ActivitiesSequence ActivitiesEstimate Activity DurationsDevelop Schedule | - | Control Schedule | - |
| Cost | - | Plan Cost ManagementEstimate CostsDetermine Budget | - | Control Costs | - |
| Quality | - | Plan Quality Management | Manage Quality | Control Quality | - |
| Resource | - | Plan Resource ManagementEstimate Activity Resources | Acquire ResourcesDevelop TeamManage Team | Control Resources | - |
| Communications | - | Plan Communications Management | Manage Communications | Monitor Communications | - |
| Risk | - | Plan Risk ManagementIdentify RisksPerform Qualitative Risk AnalysisPerform Quantitative Risk AnalysisPlan Risk Responses | Implement Risk Responses | Monitor Risks | - |
| Procurement | - | Plan Procurement Management | Conduct Procurements | Control Procurements | - |
| Stakeholder | Identify Stakeholders | Plan Stakeholder Engagement | Manage Stakeholder Engagement | Monitor Stakeholder Engagement | - |
By Knowledge Area
| Knowledge Area | Covered | Partial | Out-of-Scope | Procs w/ output Gap | Total |
|---|---|---|---|---|---|
| Integration | 6 | 1 | 0 | 0 | 7 |
| Scope | 6 | 0 | 0 | 0 | 6 |
| Schedule | 5 | 1 | 0 | 0 | 6 |
| Cost | 4 | 0 | 0 | 0 | 4 |
| Quality | 3 | 0 | 0 | 0 | 3 |
| Resource | 5 | 0 | 1 | 0 | 6 |
| Communications | 3 | 0 | 0 | 0 | 3 |
| Risk | 6 | 0 | 1 | 0 | 7 |
| Procurement | 1 | 0 | 2 | 0 | 3 |
| Stakeholder | 4 | 0 | 0 | 0 | 4 |
Top gaps (proposed REQs)
Each gap below is in scope but not yet covered by any approved requirement. Suggested REQ-FUN-* IDs continue the existing numbering (gap-closure round took numbering through REQ-FUN-145 (approved 2026-05-11)).
Governance-covered processes
These established project management guidelines processes are handled by the project subsidiary plans (doc/project-management-guidelines/*.md) rather than by a software feature. They are still established_guidelines_covered, just not via a REQ row.
- Integration / Develop Project Charter:
doc/project-management-guidelines/00_project_charter.md (self-hosted charter) - Integration / Develop Project Management Plan:
doc/project-management-guidelines/02_project_management_plan.md (PMP for AIPM itself) - Integration / Perform Integrated Change Control:
doc/project-management-guidelines/17_change_control_plan.md - Scope / Plan Scope Management:
doc/project-management-guidelines/03_scope_management_plan.md - Scope / Define Scope:
doc/project-management-guidelines/04_project_scope_statement.md (self-hosted scope statement) - Scope / Create WBS:
doc/project-management-guidelines/06_wbs.md - Schedule / Plan Schedule Management:
doc/project-management-guidelines/07_schedule_management_plan.md - Schedule / Define Activities:
doc/project-management-guidelines/08_milestone_list.md - Cost / Plan Cost Management:
doc/project-management-guidelines/09_cost_management_plan.md - Quality / Plan Quality Management:
doc/project-management-guidelines/10_quality_management_plan.md - Resource / Plan Resource Management:
doc/project-management-guidelines/11_resource_management_plan.md - Resource / Develop Team:
doc/project-management-guidelines/11_resource_management_plan.md sec 6 - Communications / Plan Communications Management:
doc/project-management-guidelines/12_communications_management_plan.md - Risk / Plan Risk Management:
doc/project-management-guidelines/13_risk_management_plan.md - Risk / Identify Risks:
doc/project-management-guidelines/14_risk_register.md (self-hosted for AIPM) - Risk / Perform Quantitative Risk Analysis:
doc/project-management-guidelines/04_project_scope_statement.md sec 4 - Procurement / Plan Procurement Management:
doc/project-management-guidelines/15_procurement_management_plan.md - Procurement / Conduct Procurements:
doc/project-management-guidelines/15_procurement_management_plan.md - Procurement / Control Procurements:
doc/project-management-guidelines/15_procurement_management_plan.md - Stakeholder / Identify Stakeholders:
doc/project-management-guidelines/01_stakeholder_register.md (self-hosted) - Stakeholder / Plan Stakeholder Engagement:
doc/project-management-guidelines/16_stakeholder_engagement_plan.md
Notes on judgement calls
- Manage Project Knowledge is rated Partial (not Covered) because the in-project Lessons Learned Register is missing, even though cross-project knowledge transfer flows through MAS soul rows (canonical per Rule G-002).
- Perform Integrated Change Control is rated Partial because while the policy and audit log are present, no first-class change_request entity exists. The Change Log artifact (established project management guidelines distinct from audit log) is a Gap.
- Develop Team is intentionally Out-of-Scope: HRMS-style features (training, recognition, team-building) are not what AIPM is for; resource-management plan section 6 captures the narrative.
- Perform Quantitative Risk Analysis is intentionally Out-of-Scope per scope statement section 4 (Monte Carlo excluded).
- Procurement KA (all 3 processes) is Out-of-Scope by design - 15_procurement_management_plan.md section 1 explicitly states no active procurements. Templates retained on file.