CAPM Practice: Determine how project methodologies influence business analysis processes

Predictive BA quality metrics include: requirements review defect density, rework rates from requirements errors, and documentation completeness scores. Agile BA quality metrics include: stories accepted vs. rejected by product owner, escaped defects traced to requirements gaps, and customer satisfaction with delivered features.

**Why not A:** Business analysis quality is measured in every methodology, though the specific metrics and approaches differ. Agile methodologies may emphasize working software and stakeholder satisfaction, while predictive approaches may focus on requirements traceability and defect rates. Claiming quality is never measured ignores established BA practices.

**Why not B:** Quality measurement approaches are not identical across all methodologies. Agile frameworks tend to use iterative feedback loops, acceptance criteria validation, and velocity-based metrics, whereas waterfall approaches rely more on formal reviews, sign-offs, and defect density analysis. The methodology shapes which quality indicators are prioritized.

**Why not C:** While testing teams play an important role in validating solution quality, BA quality measurement is not exclusively their responsibility. Business analysts, product owners, stakeholders, and project managers all contribute to assessing whether requirements are complete, correct, and delivering expected business value.