CAPM Practice: Determine how to document project controls for an adaptive project

Inspect and adapt happens continuously in agile — at the daily Scrum (process), Sprint Review (product), Sprint Retrospective (process), and at higher levels. This multi-frequency feedback loop is the core agile control mechanism.

**Why not A:** A one-time review at phase end describes a gate review in predictive (waterfall) project management, not the agile inspect-and-adapt cycle. Agile's inspect-and-adapt principle is characterized by its high frequency and multiple cadences, not by infrequent phase boundaries. Limiting inspection to phase gates would eliminate the continuous feedback loops that agile depends on for course correction.

**Why not B:** Inspect and adapt is a team-level process discipline built into Scrum ceremonies, not a financial audit function. Finance departments conduct audits for compliance and accuracy, which is a separate governance concern from the agile control mechanism of examining product and process quality to drive continuous improvement. Conflating the two misidentifies who performs the activity and why.

**Why not C:** External auditors review compliance with standards and regulations, which is fundamentally different from agile's inspect-and-adapt cycle. Annual external audits are far too infrequent and too narrowly scoped to serve as an empirical control mechanism for iterative development. Inspect and adapt is performed by the team itself at daily, sprint, and release cadences.