CAPM Practice: Determine how to follow and execute planned strategies or frameworks

Iterative delivery involves releasing working increments at regular intervals, allowing for feedback and adaptation. This directly executes the planned iterative strategy.

**Why not A:** Focusing on documentation first and switching to development later describes a waterfall approach, not an iterative delivery strategy. Iterative delivery produces working increments at regular intervals, integrating development and documentation throughout the process.

**Why not C:** Delivering all features at the end after complete testing is a predictive or big-bang delivery approach, not iterative delivery. The iterative strategy specifically calls for releasing working increments at regular intervals, not accumulating all features for a single final release.

**Why not D:** Waiting for all requirements to be finalized before development contradicts the iterative approach. Iterative delivery works with evolving requirements, releasing increments regularly and incorporating feedback. Requiring complete requirements upfront is a predictive approach characteristic.