CAPM Practice: Determine how project methodologies influence business analysis processes

Requirements quality metrics adapt to methodology: waterfall uses formal review defect counts and completeness measures; agile uses outcome-based measures like escaped defects (requirements that were unclear led to production bugs), story cycle time (unclear requirements require more rework), and sprint review rejection rates.

**Why not A:** Both agile and traditional methodologies measure requirements quality, though they do so differently. Waterfall projects measure quality through formal reviews, traceability matrices, and sign-off processes. Claiming only agile measures quality ignores the extensive verification and validation practices built into plan-driven approaches.

**Why not C:** Requirements quality measurement is not exclusively the responsibility of the QA team. While QA plays an important role in validating that delivered solutions meet requirements, the BA is primarily responsible for ensuring requirements themselves are complete, consistent, unambiguous, and testable. Quality is a shared responsibility that begins long before QA involvement.

**Why not D:** Metrics for measuring requirements quality are not identical regardless of methodology. Agile teams may track story acceptance rates, sprint defect counts, and backlog refinement velocity, while waterfall teams may use requirements traceability coverage, defect density per requirements document, and formal inspection defect rates. The methodology shapes which metrics are most meaningful and when they are collected.