Product Backlog Grooming

A backlog that stays ordered, sized and current: one owner and ticket standards, weekly refinement and triage, splitting and estimation skills, clean-up decisions and situations from solo developers to platform teams.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Backlog Grooming, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Product Backlog Grooming

Keeping the backlog ordered, sized and free of stale tickets so each sprint starts from well-understood, ready work.

  1. Backlog inventory and ticket count baseline
  2. Named backlog owner and decision rights
  3. Consolidating scattered to-do lists into one backlog
  4. Backlog workflow states and board columns
  5. Ticket template with problem and acceptance criteria
  6. Definition of ready checklist
  7. Label, component and issue type scheme
  8. Intake route for new backlog requests
  9. Bug severity and priority definitions
  10. First stale ticket purge
  11. Weekly backlog refinement session
  12. Twice-weekly new ticket triage
  13. Ready work buffer of one to two sprints
  14. Bug triage rotation among engineers
  15. Monthly stale and duplicate ticket sweep
  16. Technical debt share in every sprint
  17. Dependency and blocker watch list
  18. Closing the loop on declined requests
  19. Quarterly backlog health review
  20. Top twenty ordering pass before planning
  21. Splitting user stories into vertical slices
  22. Writing testable acceptance criteria
  23. Relative estimation with planning poker
  24. Spikes and timeboxed research tickets
  25. Writing bug reports engineers can reproduce
  26. Sequencing backlog items around dependencies and risk
  27. Facilitating refinement so engineers do the talking
  28. Challenging unclear tickets as an engineer
  29. Backlog bankruptcy for an oversized backlog
  30. Choosing points, sizes or no estimates
  31. Ideas parking lot outside the delivery backlog
  32. Ticket age limit and auto-close rule
  33. Reducing sprint carry-over at the source
  34. Issue tracker fields and automation clean-up
  35. Making unplanned work visible in the backlog
  36. Pre-quarter backlog reset workshop
  37. Team ticket bash clean-up day
  38. Pre-release bug backlog freeze
  39. Issue tracker migration cut-over
  40. Post-incident action items in the backlog
  41. Inheriting a backlog from a departing product manager
  42. Solo developer backlog for a one-person product
  43. Open-source issue tracker grooming for maintainers
  44. Platform team backlog with many internal requesters
  45. Client-visible backlog for agency and contract teams
  46. Asynchronous refinement across time zones
  47. Merging two team backlogs after a reorganisation
  48. Throughput forecasting from backlog data
  49. Backlog ageing and flow analysis
  50. Coaching other teams on backlog refinement

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Backlog inventory and ticket count baseline

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before changing anything, count what is actually there: how many open tickets, how old they are, how many have no description or no estimate, and how many nobody has touched in six months.

First tasks

  • Export all open tickets with created and last updated dates to a spreadsheet
  • Count open tickets by age band, under three, three to twelve and over twelve months
  • Count tickets with no description, no estimate or no assignee
  • Write the baseline numbers on one page and share it with the team

Named backlog owner and decision rights

When everyone can reorder the backlog, the order means nothing and the top changes with whoever spoke last. Naming one person who owns the order, usually the product manager or product owner, and writing down who else can add, edit, close or reorder tickets, settles arguments before they start.

First tasks

  • List everyone who currently reorders or closes tickets in the backlog
  • Agree the backlog owner and a deputy with the engineering lead
  • Write a rights table for creating, editing, closing and reordering tickets
  • Restrict reorder permissions in the tracker if the tool allows it

Consolidating scattered to-do lists into one backlog

Work hides in spreadsheets, chat threads, a designer's notebook and the sales team's wish list, so the official backlog is never the whole picture. Pulling every list into one tracker and retiring the rest means refinement covers all the work, and nothing surprises the team halfway through a sprint.

First tasks

  • Ask each team member where they keep work items outside the tracker
  • Move live items from each side list into the tracker with a source label
  • Mark each retired list read-only with a link to the backlog
  • Ask the agent to compare the side lists with the tracker and flag likely duplicates

Make it yours.

Install Product Backlog Grooming, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.