CAPM Practice: Determine how to conduct stakeholder communication

Feedback loops close the communication cycle. Stakeholder reactions to requirements, sprint reviews, and prototypes provide information that improves subsequent communications and refines requirements. Without feedback, communication is a monologue rather than a dialogue.

**Why not A:** Sending the same communication to multiple stakeholders simultaneously is a broadcast distribution technique, not a feedback loop. A feedback loop specifically involves receiving and processing responses to communications — it is about bidirectional exchange, not the number of recipients or channels used for outbound messaging.

**Why not B:** Feedback loops are valuable in all project methodologies, including predictive approaches. In traditional projects, stakeholder reviews, stage-gate approvals, and inspection meetings all serve as feedback mechanisms. The need to capture and incorporate stakeholder responses is universal, not exclusive to agile environments.

**Why not C:** Automated error reporting systems are a technical monitoring tool that tracks software behavior, not a stakeholder communication mechanism. A feedback loop in the BA and communication context refers to the human process of receiving, interpreting, and acting on stakeholder responses — not system-generated error logs or technical alerting pipelines.