Skip to content

Latest commit

 

History

History
71 lines (48 loc) · 1.59 KB

Coaching CheatSheet.md

File metadata and controls

71 lines (48 loc) · 1.59 KB

#Coaching Tips

  1. Where to sit
  • Back of the room, the focus isn't about you
  1. main goal
  • to get the group to mob
  1. The 2 big questions

  2. does it work?

  3. does it smell?

  4. engagement

  • quiet = bad
  • head orientation (should be looking at the tv/projector)
  • laptops , smart-phones = bad
  • movement = increased focus (make people stand up and rotate around the table)
  • across the table = louder
  • is the navigator navigating (good) is the driver thinking (bad)?
  1. rotation time
  • more people less time
  • new people less time
  • between 4 - 10 minutes is absolute method
  1. talk in questions
  • your goal is to bring things out of people not be a navigator
  1. direct talking
  • if you have to introduce something, try to talk to the navigators not the driver
  1. line numbers
  • should be on
  1. encourage participation
  • Positive reinforcement whenever appropriate
  • no rat holes, force a decision and go
  • no abstract conversations, get to the work
  1. end while still happy
  • 2 hours max
  • don't stay late
  1. frequent check-ins

  2. what's the smell

  • build habit of looking at code and asking if it is ok
  1. admitting I don't know
  • build habit of
  1. Retrospectives
  • ask for observations
  • group by similar
  1. more process when needed
  • Lean into process when things are hard/new
  • Go light on process once things are manageable
  1. walk away
  • take bathroom break/get water give team time to be without you there (not long 5-10 minutes at a time)
  1. Small steps
  • small steps for code
  • don't skip the steps in your thought process