The Scrum Board: Visualizing the Sprint's Workflow
A Scrum board is a visual snapshot of a team's work in a sprint, making progress and bottlenecks obvious. Teams use it to track tasks from "To Do" to "Done," ensuring alignment. The footgun: mistaking the board for Scrum itself; it's a helpful tool, not.
The mental model
A Scrum board is a physical or digital visualization of the Sprint Backlog. It's a tool for making work and its flow visible to the entire team and its stakeholders. Its primary purpose is to increase transparency and facilitate communication during a sprint. It answers the question "What are we working on, and where is it in our process?" for everyone at a glance.
How it works
The board is divided into vertical columns representing the stages of a team's workflow. A simple version has three columns: "To Do," "In Progress," and "Done." Each work item from the Sprint Backlog is a card. As a team member starts an item, they move its card from "To Do" to "In Progress." When the work is completed according to the Definition of Done, the card moves to "Done." Teams often customize columns to match their process, adding stages like "Code Review," "Testing," or "Ready for Deployment."
When to use it
Use a Scrum board to manage the flow of work within a single sprint. It's the focal point for the Daily Scrum, helping the team coordinate its activities and identify impediments. It's also a powerful information radiator, providing a constant, real-time status update that reduces the need for separate status meetings.
When not to use it
A Scrum board is not a long-term project plan or a product roadmap; those are managed with the Product Backlog. It is also not a tool for a manager to assign tasks. The Development Team pulls work from the "To Do" column as they have capacity, which promotes self-organization. The board reflects the team's plan, it doesn't dictate it.
One canonical example
A team's board has four columns: "Sprint Backlog," "In Progress," "In Review," and "Done." During the Daily Scrum, a developer moves a user story card from "In Progress" to "In Review." Another developer sees this and knows it's ready for a peer code review. This visual flow prevents work from piling up. A key insight from the Scrum framework is that while this board is immensely useful, it is not a formal artifact like the Product Backlog or Sprint Backlog. It is simply a common practice.
Interview question
What is the primary function of a Scrum board during a Sprint?
- a.To replace the Product Backlog by detailing all features to be developed.
- b.To serve as the official, long-term project plan for stakeholders.
- c.To enable the Scrum Master to assign tasks to individual team members.
- d.To provide a real-time visual representation of work progress and facilitate team coordination.Correct
Why? this is the answer
The Scrum board's primary purpose is to visualize the Sprint Backlog's work flow, increasing transparency and facilitating communication and coordination within the team. It is explicitly stated not to be a long-term project plan or a tool for managers to assign tasks.
Just read this? Test yourself on what you have been reading.
Read the original → resources.scrumalliance.org
- #agile
- #scrum
- #project management
- #workflow
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles