A year of mob programming tips and tricks
summary
Team runs mob programming every workday for over a year and reports concrete gains: throughput rises from 12 to 50 tickets per month and deployments average 5–6/day (peaks ~60). Practices include strong-style pairing, enforced trunk-based continuous deployment with Jenkins delivery pipelines and live production monitoring, strict TDD, and a git commit hook that requires listing all contributors on the second commit line. Timers evolve from 6‑minute turns to Pomodoro 25/5 cycles and a simple checklist and shared Linux/IntelliJ setup keep flow.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:22A meal of a henhouse
- 1:00Flow
- 2:04Coding Standards
- 4:09Zombie Programming
- 5:59Pomodoro Technique
- 7:02Checklist
- 8:38Strong powering
- 11:15Write test first
- 12:26Team area
- 13:54Continuous delivery
- 14:53When to use branches
- 17:00Benefits of mob programming
- 17:47Working in parallel
- 18:50Collective skills
- 19:04Example
- 21:43Meetings
- 25:10Team size
- 26:07Definition of done
- 27:38Weekly refinement meetings
- 28:05Production deployments
- 28:49Working as a team
- 29:42Working at home
- 31:00Roles
- 32:12People
- 33:32Team
- 34:59Conflicts
- 36:42Running smoothly
- 37:57Team lead
- 38:50Product owner
- 39:52Teams
- 41:04Full sprint
- 41:43Standup
related talks
37mLearning technical practices using mob programming
14mMob and Extreme Programming: REX from a Junior Developer
50mMob Programming, A Whole Team Approach
01h 04mAdvanced Software Teaming
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
46mMob Programming, the True Approach to Team Development
12mMOB Programming as Equilibrium
24mtalks about joining a MOB