CAPM Practice: Explain when it is appropriate to use an adaptive approach

Adaptive approaches require active, ongoing stakeholder involvement — especially the product owner or customer representative. Sprint reviews require stakeholder attendance for feedback. Backlog refinement sessions involve stakeholders in clarifying requirements. This continuous engagement is a feature, not a burden — it's the mechanism by which the product stays aligned with real needs throughout development.

**Why not A:** While product metrics are valuable, they cannot replace human stakeholder judgment on priorities, business context, and strategic direction. Metrics inform decisions but do not make them — stakeholders provide the business perspective that data alone cannot capture.

**Why not B:** Limiting stakeholder involvement to initiation and closure would deprive the project of ongoing feedback, priority adjustments, and course corrections. This is a predictive mindset where requirements are fixed upfront, which contradicts adaptive principles.

**Why not D:** Minimizing stakeholder involvement to reduce scope change actually increases risk — without regular feedback, the team may build the wrong product. Adaptive approaches view scope changes driven by stakeholder feedback as valuable course corrections, not threats.