Backlog grooming: how to clean up a backlog nobody wants to open

Every backlog rots. Tickets get filed and forgotten, the person who cared leaves, three people report the same bug in three different words. Eventually nobody opens the backlog because opening it feels bad — and then planning happens from memory instead.

What "rotten" actually looks like

A backlog going bad shows specific, findable symptoms:

• Stale — no activity in 60+ days. If nobody's touched it in two months, it isn't planned work.
• Unowned — nobody assigned, sitting in an active column.
• Unestimated — no size, so it can't be planned into a sprint.
• Overdue — a due date in the past that nobody has moved. Every one of these teaches the team that dates are decorative.
• Duplicated — near-identical titles filed weeks apart.
• Orphaned — no epic, no parent, no context for why it exists.

The first cleanup

Block ninety minutes once. Don't try to fix everything:

• Close anything stale that isn't a real commitment. If it matters, someone will file it again — and that's information, not a loss.
• Merge duplicates, keeping the one with the best description.
• Give every remaining ticket an owner or delete it. "Someone should" is not an owner.
• Clear every past due date. Either re-commit to a real date or remove it.
• Estimate only the top twenty. Nothing below that will be planned soon enough for an estimate to survive.

A useful test: if this ticket were deleted right now, would anyone notice within a month? If not, it's not a backlog item — it's a note.

Keeping it clean

The reason the two-hour weekly grooming meeting exists is that nobody looks at the backlog in between. Two habits work better:

• Groom the top, not the whole thing. The next two sprints' worth needs to be sharp. Everything below that only needs to be findable.
• Make rot visible. If nothing surfaces stale and unowned tickets, they accumulate silently until the next big cleanup.

Scoring your backlog

Because these symptoms are all measurable, a tracker can find them for you. VectorKan grades each project's backlog out of 100 and lists exactly what's dragging the score down — stale, aging, unowned, overdue, unestimated, orphaned, duplicated — then lets you fix them in bulk rather than opening tickets one at a time.

The number matters less than the direction. A backlog at 60 and climbing is fine. One at 85 and falling every week is telling you something before your planning meeting does.

Give yourself permission to delete

The hardest part of grooming isn't finding bad tickets — it's closing them. Teams treat a filed ticket as a promise. It isn't. It's a suggestion from a version of your team that had less information than you have now. Closing it is a decision, and an out-of-date backlog is a worse artifact than a short one.