Backlog & requirements team session

Before the session

Read Days 31, 34 and 37 (about five minutes each), or Module 4 on the cheat sheet.

The 30 minutes

1. 0–5 minOpen

   Quick round: name one piece of our work that turned out bigger than we thought.

2. 5–15 minDiscuss three days
   • Day 31: A story is a promise to talk.Which of our stories were written without a conversation, and what did that cost us?
   • Day 34: Slice it vertically.Which big item in our backlog could we slice so the first piece is usable on its own?
   • Day 37: Done means done.What does done mean for us today, and where does it quietly mean different things to different people?
3. 15–25 minExercise: Slice it thin

   Pick the biggest item in the backlog. Split it by path, channel, data type or rule until the first slice is small and usable end to end. Cross out any slice that is just one technical layer.

4. 25–30 minAction for the week

   Each person writes down what done means to them, in five lines or fewer.

   Agree the team rule: “Done means usable. Written down. Every time.”