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

Retrospective improvements must be actionable — not just documented. Best practice is to select 1-3 specific, actionable improvements to implement in the next sprint. Small, frequent improvements compound over time. If retrospective findings are only documented without being implemented, the retrospective becomes meaningless and team trust in the process erodes.

**Why not A:** Waiting until project close to document improvements defeats the purpose of agile retrospectives. Retrospectives exist to enable continuous improvement within the project, not to create a historical archive. Improvements documented only at close provide no benefit to the current project.

**Why not C:** Saving all improvements for a single batch implementation at the end misses the entire point of iterative improvement. Small, frequent changes compound over time and are easier to implement than large-scale process overhauls. This approach would also accumulate frustration as known problems persist.

**Why not D:** Reporting to management for approval creates an unnecessary bottleneck and removes team ownership of their own process. Self-organizing teams should be empowered to implement process improvements within their sphere of influence without management gatekeeping.