Sprint Board: How to Spot a Sprint Goal at Risk
TeamBoard Editorial
A practical way to read your sprint board: spot stalled work, unclear ownership, and accumulating tasks, then make decisions that protect the sprint goal.

A sprint board can look busy while the sprint goal remains out of reach. Moving cards between statuses is not enough to judge progress. The more useful question is: what is ready to deliver, and what is preventing the remaining work from being completed?
Imagine a sprint whose goal is to prepare and test a service request form. The work includes defining the fields, building the form, reviewing messages, and testing submission. Halfway through the sprint, the field design is complete, but implementation is waiting for a decision about the required data. There is a clear risk despite activity on the board.
Start with the goal, before counting cards
The team may finish several small changes while the work that achieves the goal remains blocked. Review the cards essential to the desired outcome first. Completing a cosmetic change does not carry the same weight as testing submission when the sprint depends on a working form.
Look for three warning signs
Too much work started and unfinished
Review the team’s ability to finish the work it has opened. Starting another task may increase waiting instead of bringing delivery closer.
A task waiting for a decision with no one following up
Name the decision needed and identify who will follow it up. “Waiting for a reply” does not explain who is responsible for removing the blocker.
A large card with no reviewable result
Break it into parts that can be checked. For example, review the fields first, then validation messages, then submission, instead of waiting for all implementation to finish.
Turn each warning sign into a decision
Implementation is waiting for field approval: Ask who will settle the requirements and when. Assign someone to follow up and explain the impact of waiting.
Several cards are in progress: Identify the nearest deliverable the team can complete and focus on finishing it before starting more work.
Form testing has not started: Check whether enough time remains for review, and discuss scope or priorities early.
These are operational decisions for the team, rather than automatic alerts assumed to come from the tool.
Apply the review in TeamBoard
Use the backlog to separate candidate work from work selected for the sprint, then review the sprint, board, status, and owner. When a task’s situation changes, update its details so the board remains useful for decisions. Subtasks can help make the parts of a deliverable clear.
At the end of the sprint
Review how much of the goal was achieved, then understand why work remains. Unfinished work can have different causes: a delayed decision, an unsuitable estimate, or a new requirement. Use the cause to improve selection and review in the next sprint.
Start your next review with one question: which task threatens the sprint goal now, and what decision would help it move forward? To prepare the cycle from the start, explore sprint planning.