A Story of Mob Programming, Testing and Everything
summary
A cross-functional team runs an experiment of five sessions to try ensemble work, then adapts rotations from timers to rotate per task and drops the strict driver rule. The approach breaks a single-person infra silo: the team moves services to AWS and Kubernetes, automates and documents the setup, and succeeds. Practical problems include room and keyboard layout friction and remote driving, and the team settles on ad hoc ensembles two to three times a month.
AI-written summary · about
chapters (9)
- 0:00Welcome and introduction
- 4:40Story begins and team discovery
- 17:07First ensemble experiment
- 25:10Infrastructure knowledge silo challenge
- 28:44Impact on team and personal growth
- 36:25Addressing doubts and questions
- 48:48When to ensemble and when not
- 51:16How to start your own ensemble
- 1:00:00Q&A session
related talks
51mA Story of Mob Programming, Testing and Everything -
48mMob Programming: A whole team approach
52mHow to win with automation and influence people
44mExploratory Testing - MobTesting, BugBashing, CrowdTesting, Oh, My!
25mProgramming to the extreme
55mTest Management Revisited
36mContext-driven Agile Tester
40mClosing Keynote