When an Adaptive Approach Fits

An adaptive approach plans in short cycles and welcomes changing requirements, which makes it a strong fit when the end product isn't fully known up front — new product development, or any work where learning as you go genuinely improves the outcome. The trade-off: adaptive approaches can be harder to predict a fixed cost or end date for, which is exactly where predictive approaches are stronger. Neither approach is universally "better" — CAPM frames the choice as fit-for-context, and this task is where that judgment gets tested directly.

Adaptive approaches tend to thrive in organizational structures that support fast, informal decision-making — co-located or virtual teams with flat, collaborative structures — more than in rigid hierarchical ones where every decision needs layers of sign-off. Organizational process assets (an organization's existing templates, historical data, and lessons learned) and enterprise environmental factors (things like company culture, marketplace conditions, or available tools) can either support or work against adopting adaptive methods, and recognizing which is which in a scenario is the enabler being tested.

Study focus: a scenario describing stable, well-understood requirements paired with a strict regulatory approval process is signaling "predictive," even if the word "agile" appears elsewhere in the question — read for the actual conditions described, not for buzzwords.