CAPM Practice: Explain the components of an adaptive plan

Re-estimation is appropriate when new information materially changes the team's understanding: technical discovery changes the implementation approach; dependencies are identified; the story scope is clarified or expanded. Automatic re-estimation of all backlog items every sprint wastes time. Targeted re-estimation, triggered by new information, keeps estimates useful without excessive overhead.

**Why not B:** The development team owns estimates, not the product owner. The team should proactively re-estimate when they discover significant new information, without waiting for explicit PO direction; deferring entirely to the PO contradicts team ownership of the technical work.

**Why not C:** Retrospectives focus on improving team processes and collaboration, not on backlog refinement or re-estimation. Re-estimating every backlog item every sprint creates excessive overhead for stories that have not changed and provides no accuracy benefit.

**Why not D:** Estimates in agile are informed guesses that improve as understanding grows. Refusing to update estimates when material new information emerges leads to inaccurate forecasts, poor sprint planning, and a false sense of certainty — adaptive estimation is a core agile principle.