HKSM

A real-time visual board that shows the current status of sprint tasks across To Do, In Progress, and Done, maintained by the Scrum Team. It is refreshed during and after the Daily Standup and serves as both an output of that meeting and an input to tracking, review, and validation activities.

Key Points

• Represents the live status of sprint tasks and their movement across columns.
• Output of Conduct Daily Standup and ongoing team updates; input to tracking and review processes.
• May be physical or electronic, but must be visible to the team and stakeholders.
• Links with the Sprint Burndown Chart and the Impediment Log for accurate progress and issue tracking.
• Owned and updated by Developers; the Scrum Master facilitates but does not manage task content.
• Shows task ownership, remaining effort, blockers, and alignment with the Definition of Done.

Purpose

The Updated Scrumboard provides transparency and shared understanding of current sprint work. It helps the team quickly identify bottlenecks, manage flow, and make informed decisions during and after the Daily Standup.

It also gives stakeholders a simple view of progress and readiness for demonstration, enabling timely intervention when impediments or risks appear.

Key Terms & Clauses

• Columns: At minimum To Do, In Progress, Done; teams may add Testing or Blocked columns as needed.
• Task Card: Includes task title, link to user story, owner, estimate/remaining hours, and blocker indicator if applicable.
• WIP Limits: Optional constraints on In Progress items to reduce multitasking and improve flow.
• Swimlanes: Rows grouping tasks by user story, priority, or team area.
• Blocker Indicator: Visual cue that triggers entry or update in the Impediment Log.
• Definition of Done: Criteria that must be met before a task moves to Done.

How to Develop/Evaluate

1. Initialize the board at sprint start with tasks from the Sprint Backlog, ready in To Do and grouped by user story.
2. During Daily Standup, each Developer moves tasks, updates remaining hours, and marks blockers; add new tasks discovered through work.
3. Synchronize with the Sprint Burndown Chart by ensuring remaining effort is current and consistent.
4. Quality check daily: every In Progress task has an owner, remaining time is updated, WIP limits are respected, and impediments are logged.
5. Keep it visible and accessible; the Scrum Master ensures transparency, while Developers maintain task accuracy.

How to Use

• Conduct Daily Standup: Anchor discussion on what moved, what remains, and what is blocked.
• Create Deliverables: Pull the next task from To Do; swarm on blocked or aging tasks to finish work sooner.
• Track Sprint Progress: Sum remaining hours or count tasks to inform the Sprint Burndown and spot flow issues.
• Demonstrate and Validate Sprint: Identify Done items suitable for review and clarify what will be shown.
• Retrospect Sprint: Inspect patterns (blocked tasks, column aging) to propose process improvements.
• Impediment Management: Update blocker flags and ensure entries exist in the Impediment Log with owners and due dates.

Example Snippet

Simple snapshot of an Updated Scrumboard for Sprint Day 6:

• To Do: US-12 Task - Write unit tests (5h), US-15 Task - Update UI text (2h).
• In Progress: US-12 Task - Build API endpoint (4h remaining) - Owner: Dana.
• Blocked: US-10 Task - Configure environment (3h) - Waiting for credentials - Impediment Log ID-27.
• Done: US-12 Task - Database schema updated.

Risks & Tips

• Risk: Cosmetic updates without true progress. Tip: Update remaining hours immediately after work, not just column movement.
• Risk: WIP overload and multitasking. Tip: Set and respect WIP limits; swarm to finish before starting new tasks.
• Risk: Hidden or untracked work. Tip: All work during the sprint must appear on the board, including urgent unplanned tasks.
• Risk: Stale Done items that do not meet DoD. Tip: Verify DoD before moving to Done and be ready for demo.
• Risk: Tool invisibility to stakeholders. Tip: Keep the board publicly visible and accessible to the whole Scrum Team and key stakeholders.

PMP/SCRUM Example Question

During a Daily Standup, the team reports several tasks as completed, but the Sprint Burndown Chart has not decreased. What should the Scrum Master encourage the team to do before the meeting ends?

1. Move the completed user stories directly to the product backlog.
2. Ask the Product Owner to change the sprint goal.
3. Update remaining hours and task status on the Updated Scrumboard.
4. Create a separate report explaining the discrepancy.

Correct Answer: C — Update remaining hours and task status on the Updated Scrumboard.

Explanation: The burndown reflects remaining work. Ensuring the Updated Scrumboard is accurate, including remaining effort, aligns tracking artifacts and provides a truthful view of progress.