A Scrum board is a visual way to show work during a Sprint. It can be a physical wall of cards, a shared digital board or a small view inside a delivery system. A useful board helps the Scrum Team understand progress toward the Sprint Goal, expose impediments and decide what to do next. Visual appeal alone does not make a board effective, and no specific design is required by the Scrum framework.
The official 2020 Scrum Guide defines three artifacts: the Product Backlog, Sprint Backlog and Increment, each with a corresponding commitment. A board is a technique teams may use to make Sprint Backlog work and flow visible. It does not replace the Sprint Goal, the Definition of Done or the responsibility of Developers to adapt their plan as they learn.
Below are ten practical board layouts, not a ranking of commercial software products. Each addresses a distinct work pattern. Choose only the elements that help your team make better decisions, and test whether the board stays accurate in normal use.
Start with simple layouts that expose the next action
1. Three-column Sprint board. Use To do, In progress and Done for a small team with a straightforward workflow. Put the Sprint Goal above the columns so every card can be discussed in terms of its contribution. Define when an item moves into progress and what conditions must be met before it moves to Done. This simplicity can be more useful than a board with many empty states.
The trade-off is limited visibility into work awaiting review or testing. If items consistently stall inside In progress, the team needs to understand why rather than add columns mechanically. A card in Done should reflect the team’s actual Definition of Done; finishing coding alone does not necessarily make a Product Backlog item complete.
2. Review-and-test board. Use Ready, Developing, Review, Testing and Done when code review and verification are meaningful separate steps. Explicit transition policies can prevent a card from being moved forward just to improve a visual status report. The board makes queues visible, but a large Review column signals the need to help complete existing work rather than start another task.
Do not require every ticket to pass through a stage irrelevant to the work. A documentation correction and a database migration may need different evidence, even though both must satisfy the team’s quality agreement. Keep the workflow understandable without implying that the board itself guarantees quality.
3. Blocker-visible board. Add a distinct blocked indicator or a carefully defined blocked lane to the team’s ordinary workflow. The card should name the impediment, the next action and who can help, without exposing private customer data. An item waiting on an external approval is different from one that simply has not been started. Mark that difference clearly.
Use blocked cards to prompt collaboration during the Sprint, not to assign blame. A growing blocked lane can reveal a missing dependency, insufficient permissions or unrealistic assumptions in the Sprint plan. Avoid leaving items blocked with no follow-up action or expected next review.
Design layouts around goals and scarce capacity
4. Sprint Goal-focused board. Group or mark cards according to how they support the stated Sprint Goal. Keep essential Sprint Goal work readily visible and identify optional tasks separately. This can help Developers decide whether newly discovered work deserves attention, or whether it distracts from the value the team agreed to pursue during the Sprint.
The Sprint Goal is a commitment of the Sprint Backlog under the Scrum Guide, not a decorative heading that can be ignored. A board full of completed low-priority tasks is not evidence of success if the Increment fails to deliver the intended value. Inspect the goal and actual working product during the Sprint, not only the number of moved cards.
5. Work-in-progress-limited board. Apply explicit limits to started work when the team needs to improve flow. For instance, a small team might agree not to begin a new review until existing reviews have available capacity. The exact limit should follow real capability rather than an arbitrary formula. This pattern is influenced by Kanban, which can complement Scrum but is not required to perform Scrum.
The Kanban Guide for Scrum Teams describes visualizing workflow, limiting work in progress and actively managing flow. It identifies metrics such as WIP, cycle time, work-item age and throughput. These metrics provide evidence to inspect, not proof that a particular color scheme or software subscription increases productivity.
6. Aging-work board. Highlight items that have remained in progress longer than expected. Show when each item began and the next obstacle or decision, not a public ranking of employees. Useful questions include whether the work is too large, whether a reviewer is unavailable and whether an external integration is causing a delay. An age marker can create urgency for collaboration without pretending to predict an exact delivery date.
Historical cycle-time information can inform realistic expectations, but a small sample may not support a precise service-level target. Review the range and context of previous items before deciding that a current task is unusually slow. Avoid turning the board into a surveillance tool that encourages status updates instead of progress.
Adapt visualization for different kinds of coordination
7. Dependency-oriented board. When work relies on another team or an external service, show dependencies clearly with a link or short reference attached to the affected card. A separate dependency view can show which decisions are needed before a feature can be completed. The purpose is to make collaboration actionable, not to pretend that the Scrum Team loses responsibility for achieving its Sprint Goal whenever another group is involved.
Do not copy unrelated teams’ entire backlogs into one crowded board. Track only dependencies that affect the current work, their status and the next coordination step. If a dependency is consistently late, review the planning assumptions and interface agreement rather than simply changing a card’s color.
8. Remote and asynchronous team board. Use a shared digital view with consistent item identifiers, clearly defined column meaning and concise updates that explain what changed. Link to source documents and decisions rather than pasting long discussions into the card. When the team works across time zones, record enough context for the next collaborator to act without waiting for a live call.
A usable digital board must support keyboard navigation, accessible names, visible focus and sufficient contrast. Color should not be the only indicator of blocking or priority. An interface that is attractive to one participant but unusable with assistive technology fails the goal of shared transparency.
9. Multi-disciplinary delivery board. Show the flow of work that involves design, development, documentation and verification, without treating specialists as isolated silos. A team may need explicit steps for accessibility testing or security review when the product requires them. Discuss responsibility and handoffs before adding a new column for every job title.
Scrum describes a cross-functional Scrum Team rather than separate status-reporting teams inside the Sprint. When a work item stalls between functions, the board should help the Developers find a way to finish it. Splitting one outcome into many tiny cards solely for the appearance of activity can conceal that nothing releasable has been produced.
10. Urgent-work exception board. Some teams must respond to production incidents while pursuing Sprint work. Create an explicit policy for how urgent, genuine incidents are identified and how they affect the Sprint plan. A small visual lane may help everyone see when planned work is interrupted, but it should not turn every late request into an emergency.
Record the user impact and recovery owner using an approved incident process, avoiding sensitive details on a broadly visible board. After the interruption, inspect whether the Sprint Goal remains feasible and what support is required. A visible exception policy is more honest than silently moving planned tasks out of sight.
Decide what belongs on each card
A card should identify meaningful work, not merely activity. For a Product Backlog item selected for a Sprint, it may include an understandable outcome, acceptance evidence, relevant references and the current workflow state. Tasks that support that item can be represented in ways the Developers find useful. Avoid copying a long product specification onto the board when a stable, permission-appropriate link is clearer.
Use concise identifiers and transparent policies about when work starts or finishes. If a card moves to Done without meeting the Definition of Done, the visualization is misleading. If a card changes owner, record the relevant context so the next contributor can continue. Treat the board as an aid to real coordination rather than a substitute for the working product.
Privacy matters. Do not place customer names, confidential financial information, incident credentials or security vulnerabilities into a public project card. Configure access based on the sensitivity of the information and link to restricted records through approved channels where necessary.
Use the board during Scrum events, not instead of them
The Daily Scrum exists to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. Developers may use the board as evidence, but the event is not intended to become an individual status interrogation or a mechanical reading of every card. Ask which work needs collaboration, what changed and which next step best supports the goal.
The Sprint Review is about the outcome and product direction with stakeholders, not primarily about how many cards passed through a workflow state. The Sprint Retrospective can use blocked-work patterns and cycle-time evidence to identify process improvements. Sprint Planning may benefit from reviewing how similar work flowed, while the team must still create a coherent Sprint Goal and a workable plan.
The Scrum Master helps establish Scrum as defined and supports team effectiveness rather than acting as a board administrator who assigns tasks to everyone. Developers self-manage their plan within the framework. If a tool forces a workflow that undermines this behavior, adapt the tool or choose a simpler view.
Choose and evaluate a board without a beauty contest
Before selecting a physical or digital board, ask what problem the existing view fails to expose. Perhaps review work is piling up, urgent support repeatedly interrupts planned work, or remote participants cannot see decisions. Choose the smallest visual change that can make the constraint clear. Adding elaborate automation before the team agrees on workflow rules can make inaccurate data look more authoritative.
After using the layout for a few Sprint cycles, inspect whether the board led to clearer decisions. Did blocked items receive help earlier? Could people locate the next actionable work? Were important quality requirements visible? Did the workflow remain accessible? Compare observed outcomes rather than promising a fixed improvement in velocity or productivity.
Ten layouts illustrate different needs, but no team should implement all ten simultaneously merely because they appear in an article. A well-used three-column board can be more valuable than a highly decorated dashboard. The right design keeps actual work and its relationship to the Sprint Goal transparent, supports inspection and enables adaptation based on evidence.