📋 Backlog Grooming

Weekly Backlog Grooming Session Facilitator

Turns a raw list of backlog items into a structured 45-minute grooming agenda with discussion prompts, decisions required, and owner assignments. Built for PMs who want to run tight, outcome-driven refinement meetings.

This prompt converts an unprioritized backlog into a timeboxed 45-minute grooming agenda using a Discuss-Decide-Defer framework. It assigns discussion owners, sets explicit decision criteria, and produces a follow-up action list.

When to use this prompt

Use this when you have a messy backlog of 15-30 items and a grooming meeting on the calendar that tends to run over without producing clear decisions. The prompt assumes you have item titles, rough descriptions, and know which stakeholders will attend. It is best for Scrum teams running weekly or bi-weekly refinement. If your team uses continuous flow (Kanban) with ad-hoc grooming, adapt the timeboxing. The prompt works best when you paste in at least 10 items so the model can group them meaningfully. You will still need to sanity-check story point estimates against team velocity before committing.

The Prompt

Role: Product Manager Variables: {{team_size}}, {{product_area}}, {{backlog_items}}, {{attendees}}, {{sprint_length}} 
You are an experienced Scrum Master facilitating a backlog grooming session for a team of {{team_size}} engineers working on {{product_area}}. I will give you a raw list of backlog items. Your job is to produce a structured 45-minute grooming agenda using the Discuss-Decide-Defer framework.

Backlog items:
{{backlog_items}}

Attendees: {{attendees}}
Sprint cadence: {{sprint_length}}

Produce the agenda in this exact format:

1. OPENING (3 min) — Restate the sprint goal and grooming objective.

2. DISCUSS block (20 min) — Pick the 4-6 highest-value items that need clarification or estimation. For each, write: item title, 1-sentence context, key question to resolve, suggested discussion owner, and timebox.

3. DECIDE block (15 min) — Pick 3-5 items ready for a go/no-go call. For each, list the decision needed, the criteria, and who owns the call.

4. DEFER block (5 min) — List items that should be pushed, archived, or re-scoped, with a 1-line reason each.

5. CLOSE (2 min) — Generate a template for action items with owner and due date columns.

Flag any items that look like duplicates or are missing critical information. Keep language crisp; no fluff. Use bullet points, not paragraphs.

Example Output

1. OPENING (3 min) — Confirm sprint goal: ship onboarding v2. Grooming objective: finalize top 12 items for next sprint.

2. DISCUSS (20 min)
- Passwordless login (5 min) — Auth team blocked on SSO vendor. Question: do we scope down to magic link only? Owner: Priya.
- Welcome email redesign (4 min) — Copy unclear. Question: which segments get variant B? Owner: Marco.
- Profile photo upload (4 min) — S3 bucket permissions unresolved. Owner: Dan.
- Tour overlay (4 min) — Design spec missing empty states. Owner: Lin.
- Invite flow (3 min) — Dup of PROD-447. Flag for merge.

3. DECIDE (15 min)
- Deprecate legacy dashboard: data shows <2% WAU. Criteria met. Owner: PM.
- Move mobile parity to Q3: capacity confirmed. Owner: EM.

4. DEFER — Gamification badges (no data), CSV export (customer asked once, no pattern).

5. CLOSE — Action items template attached.

Recommended Tools

Linear and Jira both support native backlog views with parent-child hierarchies and ready-state flags, so the Discuss-Decide-Defer output maps cleanly into their status columns. ClickUp adds checklist-style grooming notes and lets you attach AI-generated agendas directly to the sprint view. All three have keyboard shortcuts that keep grooming meetings moving.

Linear74/100 Jira Software75/100 ClickUp94/100

Related Prompts

Split an Epic Into Shippable Stories

Decomposes a large epic into 5-12 independently deliverable user stories, each sized to fit within one sprint. Designed for PMs preparing multi-sprint initiatives for refinement.

Product Manager

Identify Duplicates and Stale Backlog Items

Audits a backlog of 30+ items and flags duplicates, near-duplicates, and items that have gone stale based on age and activity. Built for PMs inheriting or cleaning up a bloated backlog.

Product Manager

Estimate Story Points via Planning Poker

Facilitates a structured planning poker session by presenting each story with discussion questions, estimation prompts, and a variance analysis. Useful for distributed Scrum teams estimating asynchronously.

Scrum Master

Frequently Asked Questions

When should I use this prompt?

Use it the day before or the morning of your grooming meeting, after you have triaged new tickets from the last 1-2 sprints. It is not a substitute for prioritization work; it assumes you already have a rough ordering. If your backlog has fewer than 10 items, the Discuss-Decide-Defer structure is overkill. For grooming with a product owner and tech lead only, shorten the timeboxes by 30 percent and remove the DEFER block.

What if my team uses Kanban instead of Scrum?

Kanban teams rarely run timeboxed grooming meetings, so treat this as a continuous refinement checklist instead. Replace the 45-minute structure with a weekly 30-minute async review: paste the backlog, ask the model to produce the DISCUSS and DECIDE lists only, and drop the output into your team chat for offline comments. Skip the DEFER block; in flow-based systems, deferred items should just be archived immediately to keep WIP signals honest.