CAPM Practice: Determine how to prepare and execute task management steps

The daily standup synchronizes team members' activities — ensuring they know what each other is doing, identifying where collaboration is needed, and surfacing impediments quickly. This 15-minute daily coordination prevents communication delays from turning into multi-day obstacles. It is the team's event, not a management reporting session.

**Why not A:** Reviewing completed stories for product owner acceptance is the purpose of the Sprint Review (or ad-hoc acceptance testing), not the daily standup. Conducting formal acceptance during the standup would extend a 15-minute synchronization event into a potentially lengthy review session and blur the distinct purposes of Scrum ceremonies.

**Why not B:** Task assignment is a management function that violates Scrum's self-organizing team principle. During the daily standup, team members share what they plan to work on rather than receive assignments from a manager or Scrum Master. The team's collective ownership of the sprint backlog means members pull work rather than having it pushed to them.

**Why not C:** The daily standup is a team-owned synchronization event, not a status report to management. Scrum explicitly positions it as peer-to-peer communication among team members, and the Scrum Master's role is to facilitate and protect the event rather than collect reports. Treating it as an upward reporting mechanism undermines psychological safety and shifts focus from coordination to performance evaluation.