HKSM

A Scrumboard is a visible, real-time board showing Sprint Backlog items and their tasks as they move through workflow states. It is initialized during Sprint Planning and updated throughout the Sprint, feeding Daily Standup discussions and progress tracking.

Key Points

• Displays user stories and tasks across states like To Do, In Progress, and Done.
• Created from the Sprint Backlog during Sprint Planning and updated continuously.
• Primary input for the Daily Standup to inspect progress and blockers.
• Supports transparency and self-organization by making work visible.
• Links to the Impediment Log and informs the Sprint Burndown Chart.
• Can be physical (wall board) or digital, but must be the single source of truth.

Purpose

The Scrumboard exists to visualize the flow of work during a Sprint. It enables the Development Team to coordinate, the Scrum Master to facilitate removal of impediments, and the Product Owner to observe progress against the Sprint Goal.

By radiating current status, it reduces reporting overhead and supports empirical process control through transparency, inspection, and adaptation.

Key Terms & Clauses

• Columns: Typical states are To Do, In Progress, Testing/Review, Done.
• Swimlanes: Optional horizontal lanes grouping tasks by user story or epic.
• Cards: Story and task cards with IDs, short titles, owners/pairs, and remaining effort.
• Blocked/Flagged: A visible marker on cards to signal impediments.
• WIP Limits: Optional caps per column to maintain flow and reduce multitasking.
• Board Policies: Only team members move cards; every task must be on the board; Done aligns with Definition of Done.

How to Develop/Evaluate

Create the Scrumboard at Sprint Planning from the committed Sprint Backlog. Break each user story into tasks and add task cards under the To Do column with initial estimates or remaining effort.

• Select format: physical board with sticky notes or a digital tool; make it highly visible.
• Define simple columns that reflect your workflow and DoD checkpoints.
• Link each task to its user story ID; use color or tags for defects, spikes, or blocked items.
• Set optional WIP limits and posting rules (e.g., update remaining hours when moving a card).

Evaluate quality by checking freshness (updated daily), completeness (all work is represented), traceability (IDs tie to Product Backlog items), and flow health (no chronic WIP overload or aging cards).

How to Use

During the Daily Standup, walk the board right-to-left, update card status, adjust remaining effort, and flag blockers. Create or update entries in the Impediment Log for blocked items.

When new work emerges, add tasks to the relevant user story; when work is split or re-estimated, reflect changes immediately. Sync Scrumboard updates with the Sprint Burndown so trends match reality.

Use the board to prepare for Sprint Review by verifying that items in Done meet the Definition of Done, and to inform Sprint Retrospective by discussing flow issues visible on the board.

Example Snippet

• Columns: To Do | In Progress | Testing | Done.
• Story S-42: As a user, I can reset my password.
• Tasks under S-42:
  • T-4201 Design reset flow (owner: A, 3h) - In Progress.
  • T-4202 Implement email token (owner: B, 5h) - Blocked (email service).
  • T-4203 Write tests (owner: C, 4h) - To Do.

Risks & Tips

• Stale board risk: require updates at least daily and after finishing or starting any task.
• Hidden work risk: no off-board work; create a task for every activity tied to a story.
• Overcomplication risk: keep columns minimal; add WIP limits if work piles up.
• Tool fragmentation risk: choose one authoritative board for co-located and remote team members.
• Micromanagement risk: the board is for team control and transparency, not status policing.

PMP/SCRUM Example Question

During the Daily Standup, the team needs a real-time view of task status and blockers for Sprint items. Which artifact should they primarily reference and update?

1. Product Backlog.
2. Definition of Done.
3. Scrumboard.
4. Release Plan.

Correct Answer: C — Scrumboard

Explanation: The Scrumboard visualizes current Sprint tasks and their status and is updated during the Daily Standup. The other artifacts are important but do not provide real-time task flow for the current Sprint.