Project Management Plan
established project management guidelines definition
The integrated document that describes how the project will be executed, monitored and controlled, and closed. It is the parent document of the subsidiary plans (scope, requirements, schedule, cost, quality, resource, communications, risk, procurement, stakeholder engagement, change, configuration) and the three baselines (scope, schedule, cost).
AI_PM requirements that support this deliverable (18)
| ID | Description | Knowledge Area | Process Group |
|---|---|---|---|
| REQ-BUS-001 | System replaces ad-hoc flat-file project state for sponsor-portfolio projects | Integration Management | Initiating |
| REQ-BUS-002 | System allows established_guidelines_conformant project execution end-to-end | Integration Management | Planning |
| REQ-FUN-013 | Store attachments with id, parent_kind, parent_id, filename, content_hash, storage_uri | Integration Management | Executing |
| REQ-FUN-040 | REST API described by an OpenAPI 3.x specification | Integration Management | Planning |
| REQ-FUN-041 | REST API provides CRUD endpoints for every entity REQ-FUN-001..013 where the operation makes sense | Integration Management | Planning |
| REQ-FUN-042 | All write endpoints require a bearer token | Integration Management | Executing |
| REQ-FUN-043 | All POST endpoints accept Idempotency-Key header; same response for retries within 24h | Integration Management | Executing |
| REQ-FUN-044 | Error responses conform to documented model with code, message, details, trace_id | Integration Management | Executing |
| REQ-FUN-045 | REST API versioned via URL prefix (/v1/...); breaking changes increment version | Integration Management | Planning |
| REQ-FUN-050 | MCP server exposes tools covering 100% of REST surface (parity) | Integration Management | Planning |
| REQ-FUN-051 | MCP tools accept and return JSON schemas matching REST data model | Integration Management | Planning |
| REQ-FUN-053 | MCP server authenticates via same bearer-token mechanism as REST | Integration Management | Executing |
| REQ-FUN-081 | Actor can instantiate a template into a working artifact attached to a project | Integration Management | Planning |
| REQ-FUN-091 | Memory created in MAS appears (or referenceable) in AIPM within 1 minute | Integration Management | Executing |
| REQ-FUN-099 | Non-MCP fallback control channel via send-text and poll-output endpoints | Communications Management | Executing |
| REQ-FUN-100 | Configuration loaded as merge of global + per-project overrides; project keys win | Integration Management | Planning |
| REQ-NFR-050 | AIPM does not introduce parallel canonical store for data already canonical in MAS | Integration Management | Planning |
| REQ-NFR-061 | Documentation (help/dev/ai) updated in same change as source it documents | Quality Management | Executing |