Engineering practices team session

Before the session

Read Days 61, 63 and 68 (about five minutes each), or Module 7 on the cheat sheet.

The 30 minutes

1. 0–5 minOpen

   Quick round: one word for how our last release felt.

2. 5–15 minDiscuss three days
   • Day 61: Make releases boring.What happens between someone finishing a change and a customer having it, and which steps are still manual?
   • Day 63: Small, fast, and kind.How long do our pull requests wait for review, and how big are they?
   • Day 68: Fix the system, not the person.After our last failure, did we look at the system or at a person?
3. 15–25 minExercise: Walk the release

   Draw every step from finished code to live, from memory. Mark each step manual or automated, and note roughly how long it waits. Circle the one step that causes the most pain.

4. 25–30 minAction for the week

   Each person keeps their pull requests small this week and notes how long each one waited for review.

   Agree the team rule: “Small changes. Automated checks. Boring releases.”