CAPMHard

CAPM Practice: Validate requirements through product delivery

Question 53 of 68 in Validate requirements through product delivery

Pick an answer below — you'll get the explanation instantly, no signup.

What is 'experiment-driven development' and how does it embed requirements validation into the delivery process?

Show answer & explanation

Correct answer: A structured approach that defines hypotheses for each feature (if we build X, we expect outcome Y), delivers features as experiments, then validates requirements by measuring whether outcomes were achieved

Explanation

Experiment-driven development treats every feature as a hypothesis test: define the expected outcome, instrument for measurement, deliver, and analyze results. This systematically validates whether requirements deliver intended outcomes, enabling evidence-based decisions about what to build next.

**Why not A:** Laboratory testing of the product before deployment is a traditional QA or staging environment approach, not experiment-driven development. Experiment-driven development defines hypotheses for each feature and validates them by measuring real outcomes after delivery, not through pre-deployment lab testing.

**Why not B:** Experimenting with different programming languages is a technical evaluation activity, not experiment-driven development. This approach treats features as hypotheses about user behavior and business outcomes, not experiments with implementation technologies.

**Why not D:** Developers choosing what to build based on personal experiments describes ad-hoc development without strategic direction. Experiment-driven development is a structured approach where the team collectively defines hypotheses tied to business outcomes, instruments for measurement, and systematically validates results.

Key Concept

This question covers Validate requirements through product delivery under Validate requirements through product delivery (Business Analysis Frameworks).

All 1,500+ CAPM questions are free