Prioritisation & planning

Backlog refinement

Take the top of the backlog and make it ready: understood, sliced, estimated, with acceptance criteria.

When. A sprint planning that discovers the work is a sprint planning that overruns. Refinement is where the discovery is supposed to happen.

Duration
1.5 h
Participants
PM + the delivery team
Output
A top of backlog that meets the Definition of Ready
Stage
Pre-PMF · Post-PMF · Scale-up · Mature
Needs con…Being sli…EstimatedReadyParked
Find the right sequence

In FigJam: File → Duplicate to your drafts, then keep this workshop's section. Get the file on Figma Community

Filled example

Needs contextOffline conflict:which version wins?What counts as afinishedintervention?Being slicedFirst-run checklist,split by roleParts catalogue:scan first,catalogue laterEstimatedPre-fill first jobfrom signup, 2Bigger tap targets,1SMS invite fortechnicians, 3ReadySkip company profilestepRemove secondconfirmation screenRetry photo uploadwith backoffAlert support afterthree failed syncsParkedCustomer portal, noownerRoute planning,nobody bought it

Example data. Fieldnote is a fictional company used to fill every board, so the examples tell one consistent story.

Fieldnote, Tuesday refinement, top of the activation backlog, the week after the March photo incident.

What the team took away

Two items sat in Needs context for the third week running, both about offline rules. That repetition, not the estimates, is what got a decision session booked with Tom.

How to run it

Preparation

Agenda

  1. 5 min
    Why this item
    For each item, the PM says the outcome it serves. An item with no outcome goes back to the backlog, not into the sprint.
  2. 25 min
    Ask until it is boring
    The team asks questions until nobody has one left. Write every unanswered question on the item: those are the real blockers, and they are worth more than the estimate.
  3. 25 min
    Slice
    Anything too big gets split by outcome, not by layer. 'Backend then frontend' is two items that deliver nothing on their own.
  4. 20 min
    Acceptance criteria
    Write what has to be true for the item to be accepted, in the words of the person who will accept it.
  5. 15 min
    Ready or not
    Check each item against the Definition of Ready out loud. Items that fail stay out. Letting one through is how the next sprint overruns.

Pitfalls

Afterwards

Ready items go to sizing (Planning poker or T-shirt) then sprint planning. If the same questions keep blocking items, the gap is upstream: research or a story map.

Source : https://scrumguides.org/scrum-guide.html

Related workshops

Back to the compassAll workshopsVersion française