HKSM

A brief, daily, team-led sync time-boxed to 15 minutes where each member shares: what they finished since the last standup, what they intend to do before the next one, and any blockers. Work is often broken down so updates refer to specific tasks and impediments are quickly surfaced for follow-up outside the meeting.

Key Points

• Held every working day and limited to 15 minutes.
• Each person answers three prompts: what was completed, what is next, and what is blocking progress.
• Focuses on team coordination and exposing impediments, not on solving problems in the meeting.
• User stories should be decomposed into smaller tasks so updates are concrete and actionable.

Example

At 9:15 AM the Scrum Team meets for 15 minutes. Lina: "Since yesterday I finished the login API wiring; next I will write unit tests; I am blocked by an expired test certificate." Omar: "I reviewed the pull request; next I will implement error handling; no blockers." The Scrum Master records the impediment and schedules a separate discussion. Because the team decomposed the user story into tasks like "Integrate OAuth" and "Write tests," each update is specific and easy to track.

PMP Example Question

Which statement best describes the Daily Standup Meeting in Scrum?

1. A 60-minute manager-led status review where tasks are reassigned and problems are solved.
2. A 15-minute, team-run daily event where members state what they finished, what they will do next, and any impediments.
3. A backlog refinement session focused on decomposing epics into user stories.
4. A weekly stakeholder demo to show completed increments.

Correct Answer: B — A short, daily, team-led coordination meeting focused on progress and blockers

Explanation: The standup is time-boxed to 15 minutes and centers on the three prompts for synchronization and rapid impediment visibility; it is not a problem-solving meeting, backlog refinement, or a stakeholder review.