CAPM Practice: Determine how to conduct stakeholder communication

Push communication (emails, reports, presentations) delivers information to recipients. Pull communication (intranets, document repositories, wikis) makes information available for stakeholders to access at their discretion. Both have appropriate use cases.

**Why not A:** The push/pull distinction is not about formality. Emails can be either push (sending a report directly) or associated with pull systems (sending a link to a repository). Formality and channel type are separate communication dimensions from the push/pull delivery model described in the PMBOK communication management framework.

**Why not B:** Push and pull in stakeholder communication have no relation to version control concepts used in software development. These are project management and business analysis terms describing how information reaches stakeholders — actively delivered versus made available for retrieval — not Git or source code operations.

**Why not C:** Push and pull communication choices are driven by the nature of the information and stakeholder access needs, not by stakeholder priority or power level. High-priority stakeholders may actually benefit from pull communication (e.g., an executive dashboard they access on demand) while lower-priority stakeholders might receive pushed status updates.