Mobbing for the Win
summary
Claims that small mobs of about five people work best and groups above six get noisy, with a successful three-person pilot; mobbing uses 1 screen 1 keyboard and strict driver/navigator rotation (example hard limit: ~50 minutes). Teams take vertical slices—frontend, middleware, low level—build full-stack increments (example: a button that travels through middleware to hardware and back) and get immediate UX/product owner sign‑off. Emphasis is on shared code, fast end‑to‑end feedback, rapid learning and stronger team cohesion.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:27Introduction
- 0:44What is mobbing
- 1:05Why is one screen important
- 1:27Communication
- 1:55Roles
- 2:17Taking Turns
- 3:58Fast Feedback
- 4:11Who is the Mob
- 10:39Why Mob
- 12:58How to Mob
related talks
26mMob Programming
44mMob Programming: Learn Together. Deliver Together
01h 04mAdvanced Software Teaming
50mMob Programming, A Whole Team Approach
01h 00mMob Programming, A Whole Team Approach
46mMob Programming: A Whole Team Approach
54mMob Mentality Collaborative Coding and Problem Solving
14mGang up on difficult problems with Mob Programming
