4.1. When to Use an Adaptive Approach
💡 First Principle: Adaptive approaches aren't "better" or "more modern" in some absolute sense — they're the right fit when requirements are expected to evolve and the cost of frequent stakeholder feedback is low relative to the cost of building the wrong thing. Organizational structure either supports or fights against that feedback loop.
Weighing pros and cons. Adaptive approaches shine when early, frequent feedback can meaningfully change direction — software features, evolving customer needs, R&D-style work. Their cost is reduced predictability: stakeholders who need a fixed budget and date locked in early may find adaptive's evolving scope uncomfortable. Predictive approaches trade that flexibility for upfront certainty, which is exactly why regulated or fixed-scope work (construction, compliance-driven deliverables) leans predictive.
Organizational structure fit. Adaptive approaches depend on fast communication and shared context, which some structures support better than others.
| Organizational Structure | Adaptive Suitability | Why |
|---|---|---|
| Colocated team | High | Fastest feedback loops, easiest informal communication |
| Matrix structure | Moderate | Cross-functional access helps, but competing priorities across managers can slow decisions |
| Virtual/distributed team | Moderate-to-high, with strong tooling | Feasible, but needs deliberate communication practices to replace in-person immediacy |
| Rigid hierarchical structure | Lower | Layered approval chains slow the fast decisions adaptive delivery depends on |
Organizational process assets and enterprise environmental factors. Certain OPAs (existing agile playbooks, backlog templates, retrospective norms) and EEFs (a culture that tolerates visible in-progress work, executive sponsorship for iterative funding models) actively facilitate adaptive adoption. Their absence doesn't make adaptive impossible, but it raises the organizational friction a team has to overcome.
⚠️ Exam Trap: Don't assume any organizational structure supports adaptive delivery equally well. A scenario describing a strictly hierarchical, multi-layer approval structure is testing whether you recognize that structure as friction against adaptive practices — not a neutral backdrop the methodology choice ignores.
Adapting the practice when structure can't be changed. Not every scenario hands you an ideal colocated team. A distributed team spread across time zones, or a hierarchy that isn't going away this quarter, still needs adaptive principles applied — just with the mechanics adjusted while the underlying goal stays the same. Asynchronous written updates and staggered review windows can substitute for live standups when simultaneous meetings aren't realistic; the exam wants you to recognize that the goal is preserving fast feedback, not preserving the literal format that usually delivers it. Recognizing this distinction — adapting the mechanism while keeping the underlying principle intact rather than abandoning it — is itself a testable associate-level skill, not just a practical workaround for an imperfect situation.
