Download Mobile App
A Scrum board is a physical or digital view of the work a team has selected for its current Sprint. Start with the Sprint Goal, show work in clear states, and agree what counts as Done. The board helps the team coordinate; it is optional, not a required Scrum artifact.
This guide shows how to build a board, write useful cards and use it during the Sprint, with a small worked example. An online board is useful when teammates need access from different places, but a board does not replace their conversations.
What is a Scrum Board?
A board can visualise the Sprint Backlog: the Sprint Goal, selected Product Backlog items and the plan for delivering them. Keep the broader Product Backlog distinguishable from the work selected for this Sprint.
Digital Scrum boards offer numerous advantages, including the ability to update and show task situations in real-time. They enable teams to quickly determine in which the sprint lies and what objectives the team prioritizes.
Structure of a Scrum board
Choose columns that reflect how your team works. The following is a starting layout, not a mandatory Scrum sequence:
- To do: work selected for the Sprint that has not started. User stories are one way to describe items, not a required column or format.
- In progress: work currently being developed. Keep blocked work visible with the reason, the help needed and the next action.
- Review or testing: an optional state for work awaiting a check. Agree entry and exit rules so a card does not wait here without anyone noticing.
- Done: work that meets the applicable Definition of Done. A finished subtask does not make the whole Product Backlog item Done if required checks remain.
Types of Scrum Boards
These Scrum boards are straightforward, easy to use, and comprehend, and they do not necessitate any advanced understanding of the Scrum board's many features.
If the team chooses a board, decide whether physical or digital access best supports everyone. Consider remote participants, accessible text, update habits and where the supporting evidence will live.
Digital board
You may also organize your Sprints by creating a digital Scrum board. The advantages of a digital board include real-time updates, personalization, and increased flexibility. Furthermore, many digital applications make it simple to collect all project data by allowing you to add papers straight to the board.
Digital boards are ideal for technology groups, fast-paced organizations, teams with remote employees, or situations where shareholders and investors require updates on project status. While digital boards can alleviate some of the challenges that physical Scrum board users encounter, they will not address all of your team's communication issues.
Use the Daily Scrum to inspect progress towards the Sprint Goal and adapt the plan. It does not guarantee that every forecast item will be completed.
Physical Board
A physical board can work for a co-located team with an accessible shared space. Use readable labels rather than colour alone, and agree how people away from the room will see and update the same information.
Keep a physical board current and make blockers visible. If remote colleagues need someone else to move their cards or read the board aloud, consider a shared digital view instead.
Fortunately, physical boards encourage face-to-face communication, which is essential because Scrum depends on a close-knit team that interacts frequently and accepts their work as their own.
How to use a Scrum Board?
Although physical and digital Scrum boards have the same principle, how you use them in your everyday work may differ. Here are the steps to make your own Scrum Board:
Start with the Sprint Goal and workflow
Display the Sprint Goal where the team can refer to it. Add the selected work and a few meaningful states. Agree what moving a card means, rather than adding columns simply because a template has them.
Create cards that explain the work
Write the intended result, relevant acceptance criteria, dependencies and links to supporting information. Developers decide how to organise the work and who collaborates on it; the board is not an assignment sheet controlled by the Scrum Master.
Performing project tasks
Update a card when its state changes. During the Daily Scrum, discuss whether current work supports the Sprint Goal, what is blocked and how the plan should adapt. Finish or unblock useful work before starting more work merely to keep everyone busy.
Check Done before moving a card
Move work to Done only when it meets the team’s quality requirements. If a required review or test remains, show that honestly. Record evidence on the card so another teammate can understand what was checked.
Review the outcome and improve the process
At the Sprint Review, the Scrum Team and stakeholders inspect the outcome and discuss what to do next. The review is not a gate that must precede every release. The Sprint Retrospective then examines ways of working. Unfinished Product Backlog items return to the Product Backlog for future consideration; do not mark them Done to tidy the board.
Scrum board example: a small invitation-flow improvement
Illustrative Sprint Goal: a new workspace member can accept an invitation and reach the shared project. The team selects the following work; this is an example, not an Edworking release or customer result.
- Card 1 — Invitation email opens the correct workspace. State: Review. Check: the link opens the intended workspace for the test accounts, including an expired-invitation case. Evidence: test notes linked on the card.
- Card 2 — First-time member sees the project instructions. State: In progress, blocked. Dependency: approved onboarding text. Next action: the product owner clarifies the wording with the team today; the team checks whether another selected item can progress without it.
- Card 3 — Existing members retain access after an invitation is accepted. State: To do. Check: existing-member access tests still pass. The team considers this alongside the new-member flow before calling the increment Done.
A card can show an acceptance check for its specific behaviour, while the Definition of Done applies the shared quality standard to the increment. For example, required tests and review may apply to every change. Agree the real standard for your product; do not copy these illustrative checks as a complete quality policy.
Copyable card format: intended result; related Sprint Goal; acceptance checks; collaborators; state; dependency or blocker; next action; evidence links. Add only fields the team uses to make decisions.
The Scrum Guide defines the framework. Scrum Alliance’s board guide explains why a board can be adapted or omitted. For the team’s process discussion, use a project retrospective.
Benefits of using a Scrum Board
A maintained board makes work easier to discuss. Its value comes from the decisions it supports, not from the number of cards or updates.
Improve Team Efficiency
Use the board to spot waiting work, handoffs and places where collaboration could help. Do not rank individuals by card counts or apparent speed: items differ in size, complexity and dependencies.
Assist in Problem Assessment
A visible blocker gives the team a chance to ask for help or adapt the plan. It cannot predict every problem or make an absent specialist interchangeable with another teammate.
Helps with Effective Planning
Use experience from previous Sprints, current availability and the Sprint Goal when planning. Estimates and charts can inform the discussion but are not precise promises of individual output.
Encourage Transparency and Accountability
The team shares an up-to-date view and can explain its decisions. Developers manage their plan; the Scrum Master helps the team use Scrum effectively rather than distributing tasks as a supervisor.
Who Should Use A Scrum Board?
A Scrum Board can be a game-changer for many different types of teams and individuals. Here are some groups that can greatly benefit from using a Scrum Board:
- Scrum teams: a board may help visualise Sprint work and coordinate delivery. Teams can use another approach if it gives them sufficient transparency.
- Project teams evaluating Scrum: decide whether the framework fits the work before adopting its board. Managing multiple projects may also need a separate portfolio or capacity view.
- Remote teams: Working remotely can be a challenge, but a Scrum Board can help bridge the gap between team members. It provides a central hub for tracking tasks, sharing updates, and discussing project-related issues, making it easier to stay connected and collaborate effectively.
- Creative professionals: Whether you're a graphic designer, a writer, or a marketing guru, a Scrum Board can help you break down large projects into manageable tasks, keep track of deadlines, and ensure that nothing slips through the cracks.
Scrum board vs. Kanban board - Where is the difference?
Scrum and Kanban boards may seem similar at first glance, but they have some fundamental differences that set them apart. So, what makes them unique?
- Framework: Scrum is an agile project management framework that focuses on iterative development, while Kanban is a lean workflow management system designed for continuous improvement.
- Accountabilities: the Scrum Team includes a Product Owner, a Scrum Master and Developers. A board is a tool, not an additional accountability.
- Iterations: Scrum operates in fixed time-boxed iterations called sprints, whereas Kanban focuses on continuous flow with no predefined time limits.
- Work in progress: teams using Scrum can also adopt explicit WIP limits or other flow practices. A Sprint timebox does not prevent overload by itself. Choose policies that help the team finish work rather than applying a universal card limit.
Use an Edworking board for Sprint work
Open Tasks in the relevant space and create a list for the Sprint if that fits your setup. Add a task for each work item. Record the Sprint Goal in the linked plan and put acceptance criteria and evidence links in task descriptions.
Set the task state, assignees and other relevant fields. Use Board view grouped by state, or List view when it is easier to read. Task chat keeps questions and decisions attached to the item.
Change a task’s state or drag it between columns when the agreed condition is met. A blocked item should explain the dependency and next action. These are configurable task controls, not automatic enforcement of Scrum rules; see the Edworking task guide.
Conclusion
Start with a visible Sprint Goal, clear cards and an honest Done policy. Keep the board current enough to support the next conversation, and adjust the format when it stops helping the team.
Explore Edworking task management to see the board and list workflow, and check current plans for feature availability.
