A county digital services lead compares adaptive and predictive delivery for a benefits-application portal. Which statement best captures a common trade-off of the adaptive approach?

A common trade-off of the adaptive approach for a benefits-application portal is that adaptive delivery offers early value and frequent feedback but typically provides less fixed long-range date certainty than a predictive build with a stable baseline. Civic digital services gain usable increments sooner and can correct wrong assumptions, yet multi-year go-live certainty is often softer because scope and learning continue to evolve. That trade-off is what county digital-services leads should articulate honestly.

Claiming adaptive always guarantees a fixed go-live years in advance with zero feedback fails conceptually because that describes predictive-style date certainty and contradicts adaptive learning. Claiming adaptive forbids any working software until the final day fails because early increments of working software are a hallmark of adaptive delivery. Claiming adaptive eliminates stakeholders so no feedback is possible fails because stakeholder collaboration and feedback are central, not optional, to adaptive suitability.

Exam caveat: CAPM expects balanced trade-off recognition—benefits and limitations—rather than caricatures that adaptive is either magic certainty or anti-delivery. Operational check: for the benefits portal, publish near-term increment goals and empirical forecasts, avoid over-promising multi-year date rigidity unless hybrid predictive commitments are separately baselined, and keep feedback loops visible to sponsors.