CAPM Practice: Determine how project methodologies influence business analysis processes

BAs distinguish between outputs (what we deliver) and outcomes (what changes as a result). A CRM system (output) should improve customer retention (outcome). Focusing on outcomes keeps requirements aligned with business value rather than just delivery of features.

**Why not A:** Outputs and outcomes are distinct concepts, not synonyms. Outputs are the tangible deliverables produced by the project, while outcomes are the business changes or value achieved through using those outputs. Conflating them risks measuring delivery instead of value.

**Why not C:** Both BAs and developers contribute to outputs and outcomes. BAs produce requirements artifacts (outputs) and help define desired business changes (outcomes). Developers produce software (outputs). The distinction is between deliverables and results, not between roles.

**Why not D:** This reverses the typical usage. Project success is increasingly measured by outcomes (business value achieved), not just outputs (deliverables produced). BA performance can be measured by both the quality of their outputs and the outcomes those outputs help enable.