Skip to main content

Work

Reading a Sprint Board for Overload Instead of Progress

Your sprint board already shows who is struggling. Card age, assignee concentration and repeated carryover read as people signals, not schedule signals.

Written by Sicherhaven

Your sprint board is usually read for schedule: what is done, what is left, will it land. Read the same board for overload and three signals stand out. Card age, how concentrated the assignments are, and which items carry over more than once. Together they tell you who is stretched before that person tells you, and usually before they know how to say it.

Nothing new has to be added to the board. You are asking a different question of the same data.

Card age, not card count

A column full of cards is normal. A column full of old cards is not.

Look at how long each item has sat in its current state. An item in progress since the middle of last week is telling you something: it is blocked, it is bigger than it looked, or the person is being pulled away from it repeatedly. All three are worth a conversation, and none of them show up in a burndown, which counts what closed rather than what is stuck.

The useful habit is to sort by time in column rather than by priority once a week. The top of that list is your agenda.

Assignee concentration

Count the open items per person. Then count the ones where the same person is the only realistic owner.

Two different problems hide here. The first is simple overload: one person holding many cards while others hold few. The second is quieter and worse. One person is on the critical path for several items that other people also depend on, so their week determines everyone else's. That person often looks fine on card count and is carrying the most risk on the board.

Reviewers count too. If one person reviews everything, they are a queue even when the board shows them with nothing assigned.

Repeated carryover

Anything that has rolled from one sprint into the next twice is a signal. Three times is a fact.

Repeated carryover rarely means the person is slow. Usually it means the item was never properly understood, or it keeps losing to whatever is louder that week, or it depends on somebody outside the team who has different priorities. All of those are management problems presented as an individual's incomplete task, and the person holding it usually feels it as personal failure. Left alone it becomes one of the attrition warning signs a board shows first.

Pull those items out and ask what has stopped them each time. If the answer is different every time, it is priority churn. If it is the same every time, you have found a dependency worth fixing permanently.

The signals to distrust

Two things look like overload and often are not.

A large number of small cards can just be someone who breaks work down finely. Check the age before concluding anything.

A quiet board can mean people have stopped updating it, which is itself worth knowing but is not the same as a healthy sprint. If the board only updates the day before review, you are reading a report, not a board.

Read leave alongside the board

Half of the overload picture is missing if you cannot see who is away. A person carrying six items with two days of approved leave in the sprint is in a different position from one carrying six with a full fortnight, and most boards do not show that at all because leave lives in a different system. The combined view is what a manager wants on a Monday morning.

SicherOne is built for that: project management and HR on one set of records, so the board knows who is on leave rather than a manager checking a second place. AI agents run on those same records with the full context, and a human approves agent output before it ships. Modules are separable and it is sold per seat, and private models can be self hosted.

What to do with what you find

Do not lead with the data. Take the three signals into a one to one as questions rather than conclusions. "This has been in progress a while, what is it waiting on" gets you further than presenting somebody with their own card age.

Then act on the board rather than the person. Move an item, split it, reassign a review, or drop something. Overload is almost always a load problem, and telling someone they seem stretched without removing anything from their week is not help. It is just observation. What you find travels upward too, because board reports should say something about people and not only progress.

← All posts

We're building the future of community events and financial wellness

See how Eventify and WealthWise change the way people find events and manage money.

Get Started