HKSM

A daily, tightly time-boxed meeting where the Scrum Team quickly aligns on progress, plans the next 24 hours, and flags any impediments. It is a focused forum for team members to update one another and coordinate work toward the sprint goal.

Key Points

• Held every day at a consistent time and place; typically limited to about 15 minutes.
• Purpose is to inspect progress, plan the next day of work, and surface blockers, not to solve issues in the meeting.
• Team-focused: developers speak, the Scrum Master facilitates, and the Product Owner may participate as needed.
• Follow-up discussions happen after the standup to keep the event short and focused.

Example

At 9:00 a.m. each day, the Scrum Team meets for 15 minutes in front of the task board. Each member briefly shares what they completed since yesterday, what they will do today, and any obstacles. The Scrum Master notes two impediments and schedules quick huddles afterward to resolve them.

PMP Example Question

Which approach best reflects the purpose of Conduct Daily Standup?

1. Have each team member email detailed status to the Scrum Master to avoid meeting time.
2. Keep the meeting to about 15 minutes for team members to share progress, plan the next 24 hours, and raise impediments, then handle problem-solving afterward.
3. Use the meeting to demo finished features to stakeholders and collect approvals.
4. Extend the meeting to 45 minutes so the team can resolve all technical issues immediately.

Correct Answer: B — Hold a brief daily team sync to share progress, plan the day, and highlight blockers.

Explanation: The standup is a short, time-boxed event for team coordination and impediment visibility; detailed problem-solving and demos occur outside this meeting.