CAPM Practice: Determine how to conduct stakeholder communication

Agile's 'working software over comprehensive documentation' doesn't mean no documentation — it means sufficient documentation. BAs produce documentation that adds communication value (user stories, acceptance criteria, process models) rather than artifacts for their own sake.

**Why not A:** Producing the same level of documentation as predictive projects regardless of methodology ignores the agile principle of valuing working software over comprehensive documentation. Agile projects benefit from lighter documentation that supports communication without creating unnecessary overhead.

**Why not C:** Documenting requirements only after they have been fully implemented defeats the purpose of requirements documentation, which is to guide implementation. Some level of documentation before and during development is necessary to align the team on what to build.

**Why not D:** Producing no documentation at all in agile projects is a common misconception. The Agile Manifesto values working software over comprehensive documentation, but it does not advocate for zero documentation. Sufficient documentation remains essential for team alignment, knowledge transfer, and ongoing maintenance.