CAPM Practice: Determine how to plan project iterations

The daily Scrum is a 15-minute inspection and adaptation event for the team. It creates transparency about progress toward the Sprint Goal and surfaces impediments for quick resolution — not a status report to management.

**Why not A:** Code quality metrics and defect counts are appropriate topics for sprint reviews, retrospectives, or continuous integration dashboards — not the daily standup. The standup is deliberately time-boxed at 15 minutes and focused on coordination and impediment identification, not quality trend analysis.

**Why not B:** The daily Scrum is explicitly a team synchronization event for the team itself, not a reporting mechanism for management. Using it for performance evaluation would destroy psychological safety, cause team members to be guarded rather than transparent about problems, and transform a collaborative coordination tool into top-down surveillance.

**Why not C:** The daily standup is not a re-planning session. Completely replanning the iteration every day would destroy the sprint commitment, prevent the team from developing a sustainable cadence, and undermine the stability of the sprint goal. Day-level tactical adjustments are expected, but the sprint scope and goal remain anchored for the sprint's duration.