How to really work as a team- from sleepy to strong pair programming
summary
Teams move from bored to productive by changing how pairing actually works not by preaching collaboration Specifics: reduced WIP to 1–2 stories when mobbing, use of Live Share and 25/5 Pomodoro to keep engagement, a tight driver/navigator definition so the driver writes with understanding not mindless typing and a rotating devil’s advocate to pull people back in Remote pairing is harder but workable and pull requests become near real time reviews improving lead time and onboarding.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:32Work in Progress
- 8:40Sleepy Pairing
- 14:15Microphone Change
- 18:57Virtual Interruptions
- 33:49Bouncing Ideas
- 34:29Live Share
- 35:32Pomodoro Technique
- 43:39The Onboarding Process
- 47:19Building Psychological Safety with Colleagues
- 49:29Do You Do Anything Different Depending on the Pair Composition
- 49:51How Do We Handle Different Levels of Experience within the Pairs and Do We Pair Differently
related talks
48mHow to Really Work as a Team - From Sleepy to Strong Pair Programming
32mHow to work as a team, sleepy to strong pair programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
23mWarm-Up Talk: Perceptions of Pair Programming
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
44mWhat We Learned in 8829 Hours of Pair Programming
01h 00mMob Programming, A Whole Team Approach
28mProblem Solving Through Pair Programming