Hacking Your Processes
summary
Adopts concrete hacks: standups require prepare a post-it and start with "who needs help?" so blockers surface first; run standups ticket-first or retire them if mobs pair independently. Run daily or very frequent retrospectives that pick one small action, track time lost (build waits added up to hours), and push that action into the next sprint. Experiment with TDD to survive interruptions, rotate facilitation, and estimate on effort and risk while budgeting by value not time so rollbacks stay simple.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:50Hi, I'm Richard
- 3:03Many teams start with Scrum
- 5:24Cargo-cult
- 7:06Dark Agile
- 8:43Individuals and interactions ...over processes and tools
- 10:28Working software
- 12:05Customer collaboration ... Over contract negotiation
- 14:15Responding to change ... over following a plan
- 16:24Prepare in advance
- 17:38Flip the questions
- 18:48Walk the board
- 20:53Try different times of day
- 24:10Don't... use pressure
- 24:54Don't... wait for the standup!
- 26:35Focus on improvement
- 27:24Capture things continuously
- 29:00Make retrospectives frequent
- 30:52Don't... resort to blame
- 32:19Make sure it happens!
- 34:44Capture all the activity
- 36:02Set clear goals
- 37:35Hack the Estimates conversation
- 39:32Use scope as the variable
- 40:24Plan for small and done
- 42:08Start from a goal
- 43:01Think of ways to move towards the goal
- 43:41Know what "better" would look like
- 46:06Design your experiment
- 47:00A good experiment...
related talks
42mHow Doing the Little Things Well Makes the Big Things Possible
23mManaging diverse engineers for high-impact deliveries
55m14 Identifying And Removing Impediments
41mA Selectio of Lightning Talks
20mIn the loop but out of the hierarchy
50mMob Programming, A Whole Team Approach
38mExpect the Unexpected! A Method for Handling Unplanned Work
46mManaging The Process