HKSM

A facilitation technique used in the Daily Standup where each team member states what they completed yesterday, what they plan to do today, and any impediments blocking them. It promotes transparency, daily planning, and quick surfacing of issues to keep the sprint on track.

Key Points

• Used during the Daily Standup and time-boxed within the 15-minute meeting.
• Each developer answers three prompts: yesterday's progress, today's plan, and impediments.
• Focuses on the Sprint Goal and flow of work, not on problem solving in the meeting.
• Scrum Master notes impediments and arranges follow-ups outside the standup.
• Encourages self-organization, swarming, and accountability within the Scrum Team.
• Updates to task status and the Impediment Log typically follow immediately after the meeting.

Purpose of Analysis

The technique provides a daily inspect-and-adapt mechanism to assess progress toward the Sprint Goal. By comparing planned work to actual progress and exposing blockers, the team can re-align priorities and coordinate handoffs.

It ensures emerging risks and dependencies are visible early, so the Scrum Master and team can address them before they threaten the sprint forecast.

Method Steps

1. Prepare the visual board: make the Sprint Backlog and task board visible, along with the Sprint Goal and current burndown.
2. Form the circle: the Development Team, Product Owner as needed, and Scrum Master attend; developers speak to each other.
3. Ask the three questions: each member states what they finished yesterday, what they will do today, and any impediments.
4. Capture blockers: the Scrum Master records impediments, owners, and potential follow-ups without problem solving in the standup.
5. Align and swarm: identify handoffs, pairing, or swarming opportunities to finish user stories sooner.
6. Update artifacts: after the standup, update the task board, burndown, and Impediment Log; schedule quick huddles as needed.

Inputs Needed

• Sprint Goal and prioritized Sprint Backlog items.
• Task board or digital board showing To Do, In Progress, and Done.
• Current sprint burndown or remaining effort chart.
• Team availability and any planned time off or constraints.
• Known impediments or risks carried from previous days.

Outputs Produced

• Updated task status on the Sprint Task Board and refined daily plan.
• New or updated entries in the Impediment Log with owners and next actions.
• Micro-commitments for the day and identified collaboration plans (pairing, swarming).
• More accurate burndown trends reflecting latest remaining work.
• Shared understanding of progress and emerging dependencies.

Interpretation Tips

• Listen for alignment to the Sprint Goal; plans should reduce cycle time on near-done stories.
• Watch for aging tasks or work hopping; this signals flow problems or unclear slicing.
• Repeated impediments may indicate systemic issues needing escalation or process changes.
• Ensure answers describe outcomes, not just activity, to keep focus on value and completion.
• Encourage concise updates and defer detailed discussions to immediately after the meeting.

Example

A developer says: Yesterday I completed unit tests for User Story 5 and merged the branch. Today I will integrate with the API and verify acceptance criteria. I am blocked by missing test credentials from the security team.

The Scrum Master logs the credential issue, assigns an owner, and sets a follow-up immediately after the standup. Another developer offers to pair on the API integration to accelerate completion.

Pitfalls

• Turning the standup into a status report to the Scrum Master instead of a team synchronization.
• Problem solving during the standup, causing the meeting to run long and lose focus.
• Vague updates focused on effort rather than outcomes and progress toward Done.
• Failing to record and act on impediments, leading to repeated bottlenecks.
• Skipping participation by some team members, reducing transparency and coordination.

PMP/SCRUM Example Question

During the Daily Standup, the Scrum Master wants to improve transparency and surface blockers quickly without turning the event into a problem-solving session. Which technique should the team use?

1. Conduct a detailed root cause analysis during the standup.
2. Ask the Three Daily Questions to each developer.
3. Hold a mid-sprint Sprint Review to get stakeholder feedback.
4. Have the Product Owner provide a status briefing to the team.

Correct Answer: B — Ask the Three Daily Questions to each developer.

Explanation: The Three Daily Questions structure the Daily Standup to show progress, plans, and impediments. Root cause analysis and detailed discussions should occur after the standup, not during it.