HKSM
Daily Scrum
A short, daily team sync to review what was completed since the last meeting, state plans for today, and surface any current or expected blockers; often called the daily standup.
Key Points
- Time-boxed, lightweight event held every working day (commonly 15 minutes or less).
- Purpose is to align the team and adjust the plan for the next 24 hours, not to report status to a manager.
- Primary participants are the delivery team; Product Owner and Scrum Master may attend if it helps.
- Outputs include an updated daily plan and a clear list of impediments for removal.
Example
Each morning at 9:00, the team gathers around the task board. Maria shares that she finished the login API yesterday, plans to write integration tests today, and is blocked waiting for a test database. Others state their plans and blockers. The Scrum Master notes the database issue and commits to getting access by noon. The team adjusts the day's plan accordingly.
PMP Example Question
What best describes the primary purpose of the Daily Scrum?
- A weekly status meeting where the Scrum Master assigns tasks to team members
- A brief, daily event for the team to synchronize on progress, plan the next 24 hours, and identify impediments
- A detailed backlog refinement session led by the Product Owner
- A post-iteration retrospective to discuss process improvements
Correct Answer: B — A short daily sync to align plans and surface blockers
Explanation: The Daily Scrum focuses on team coordination for the next day and highlighting impediments; it is not task assignment, backlog refinement, or a retrospective.
