CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

A business glossary or data dictionary establishes a common language — defining terms that may have different meanings to business vs. technical stakeholders. This prevents costly miscommunication where teams think they agreed but meant different things.

**Why not B:** Cataloging all external data sources used by the project team describes a data source inventory, not a glossary or data dictionary. A glossary defines key terms to establish shared vocabulary, while a data dictionary defines data elements, types, and rules for the system being built.

**Why not C:** Translating project documents into multiple languages is a localization activity, not the purpose of a glossary or data dictionary. A glossary establishes a common understanding of terms within a single language context, preventing misinterpretation between business and technical stakeholders.

**Why not D:** Providing definitions of project management terms for new team members describes an onboarding reference, not a BA glossary. A BA glossary or data dictionary defines the specific business and technical terms relevant to the project's domain, ensuring all stakeholders share the same understanding of key concepts.