Communications Management

Ensures timely and appropriate planning, collection, distribution, storage, and disposition of project information.

established project management guidelines definition

Project Communications Management includes the processes required to ensure that the information needs of the project and its stakeholders are met through development of artifacts and implementation of activities designed to achieve effective information exchange. Comms management produces the communications management plan, the project communications themselves (status updates, notifications, the bulletin / work-board), and performance reports.

Processes in this Knowledge Area

Plan Communications Management

Outputs: communications management plan.

REQ-FUN-060 — Web UI allows browsing projects, deliverables, requirements, risks, sign-offs, work-board, audit log
REQ-FUN-099 — Non-MCP fallback control channel via send-text and poll-output endpoints
REQ-NFR-066 — Send-text/poll-output fallback channel rate-limited per agent token (60 send-text/min, 600 poll-output/min default)
REQ-STK-002 — Agent users receive consistent, machine-friendly errors and pagination (STK-003)

Manage Communications

Outputs: project communications, project documents updates.

REQ-FUN-009 — Store work-board items with id, project_id, title, description, state, claimant, posted_by, timestamps
REQ-FUN-020 — Actor (agent or human) can post a work-board item via REST or MCP
REQ-FUN-021 — Actor can claim a posted item; concurrent claims resolved deterministically with exactly one winner
REQ-FUN-023 — Actor can mark a claimed item completed
REQ-FUN-024 — Board queryable by state, project, claimant, posted-by, and date range
REQ-FUN-025 — Board delivers state changes to subscribers within 5 seconds (SSE or websocket)
REQ-FUN-026 — Claimed item cancellable by original poster or sponsor; cancellation audited
REQ-FUN-037 — Notify approvers when a sign-off is requested or delegated to them
REQ-FUN-061 — Web UI allows authoring entities a human user would create
REQ-FUN-062 — Web UI surfaces sign-off requests assigned to logged-in user
REQ-FUN-065 — Web UI allows report export (CSV, JSON) of major entities
REQ-FUN-073 — Audit log retrievable via REST and UI
REQ-FUN-095 — Progressive Web App for the sign-off page (manifest.json + service worker)
REQ-NFR-022 — Audit log exportable in CSV/JSON/NDJSON for offline analysis

Monitor Communications

Outputs: work performance information, change requests.

No AI_PM requirements primarily mapped to this process.

General Knowledge Area support

These requirements support the knowledge area broadly rather than fitting one specific process.

REQ-TRN-003 — Migration playbook present at doc/help/migration.html

Secondary support

Requirements whose primary KA is elsewhere, but which also support Communications Management.

ID	Description	Primary KA
REQ-FUN-022	Actor can hand off a claimed item to another actor	Resource Management
REQ-FUN-040	REST API described by an OpenAPI 3.x specification	Integration Management
REQ-FUN-044	Error responses conform to documented model with code, message, details, trace_id	Integration Management
REQ-FUN-050	MCP server exposes tools covering 100% of REST surface (parity)	Integration Management
REQ-FUN-063	Web UI allows approval, rejection, and delegation actions	Quality Management
REQ-FUN-064	Web UI allows audit log search by entity, actor, date range	Integration Management
REQ-FUN-097	In-process lifecycle hooks fire on board-item state transitions and sign-off lifecycle events	Integration Management
REQ-NFR-001	API median latency for read operations <= 200ms at 10 concurrent clients on reference machine	Quality Management
REQ-NFR-003	Web UI initial page load <= 3s on reference machine over local network	Quality Management
REQ-NFR-061	Documentation (help/dev/ai) updated in same change as source it documents	Quality Management
REQ-STK-003	Human users can act on the system without learning the API (STK-004)	Stakeholder Management

All requirements primarily mapped to Communications Management (19)

ID	Description	Primary Process Group
REQ-FUN-009	Store work-board items with id, project_id, title, description, state, claimant, posted_by, timestamps	Executing
REQ-FUN-020	Actor (agent or human) can post a work-board item via REST or MCP	Executing
REQ-FUN-021	Actor can claim a posted item; concurrent claims resolved deterministically with exactly one winner	Executing
REQ-FUN-023	Actor can mark a claimed item completed	Executing
REQ-FUN-024	Board queryable by state, project, claimant, posted-by, and date range	Monitoring & Controlling
REQ-FUN-025	Board delivers state changes to subscribers within 5 seconds (SSE or websocket)	Executing
REQ-FUN-026	Claimed item cancellable by original poster or sponsor; cancellation audited	Monitoring & Controlling
REQ-FUN-037	Notify approvers when a sign-off is requested or delegated to them	Executing
REQ-FUN-060	Web UI allows browsing projects, deliverables, requirements, risks, sign-offs, work-board, audit log	Executing
REQ-FUN-061	Web UI allows authoring entities a human user would create	Executing
REQ-FUN-062	Web UI surfaces sign-off requests assigned to logged-in user	Executing
REQ-FUN-065	Web UI allows report export (CSV, JSON) of major entities	Monitoring & Controlling
REQ-FUN-073	Audit log retrievable via REST and UI	Monitoring & Controlling
REQ-FUN-095	Progressive Web App for the sign-off page (manifest.json + service worker)	Executing
REQ-FUN-099	Non-MCP fallback control channel via send-text and poll-output endpoints	Executing
REQ-NFR-022	Audit log exportable in CSV/JSON/NDJSON for offline analysis	Monitoring & Controlling
REQ-NFR-066	Send-text/poll-output fallback channel rate-limited per agent token (60 send-text/min, 600 poll-output/min default)	Monitoring & Controlling
REQ-STK-002	Agent users receive consistent, machine-friendly errors and pagination (STK-003)	Planning
REQ-TRN-003	Migration playbook present at doc/help/migration.html	Closing