CAPM Practice: Determine how project methodologies influence business analysis processes

Lean Startup's build-measure-learn loop makes requirements hypothesis-driven. BAs define testable assumptions, help design minimum viable experiments, analyze measurement results, and evolve requirements based on evidence — a fundamentally different approach than requirements as fixed specifications.

**Why not A:** Requiring complete requirements documentation before any measurement contradicts the Lean Startup philosophy. The build-measure-learn loop emphasizes starting with minimal viable hypotheses and iterating based on evidence, not front-loading comprehensive documentation before learning begins.

**Why not B:** The Lean Startup approach does not eliminate the need for a BA. BAs play a critical role in defining testable hypotheses, designing experiments, analyzing measurement results, and translating validated learning into refined requirements. The BA role adapts to the methodology rather than becoming obsolete.

**Why not D:** Measuring team productivity before defining requirements confuses internal process metrics with the build-measure-learn loop. The loop focuses on validating product hypotheses with customers and users, not on measuring how the team itself performs before beginning requirements work.