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

In adaptive projects, working software IS the primary measure of progress. Sprint Reviews provide stakeholders with hands-on demonstrations of completed functionality, far more tangible than paper reports.

**Why not A:** Gantt charts are a predictive planning artifact that measure adherence to a pre-set schedule, not actual value delivered. Agile measures progress through working product, not timeline comparisons against a baseline plan.

**Why not B:** Percentage-completion metrics are notoriously unreliable and abstract — a task reported as "90% complete" may still require significant effort. Agile replaces these with demonstrated working software, giving stakeholders direct, tangible evidence of what has actually been built and tested.

**Why not D:** Velocity is an internal capacity-planning tool used by the team to forecast future sprints. Sharing raw velocity numbers with stakeholders without context can be misleading and does not demonstrate what value has actually been delivered or what the product can now do.