2015 LateRooms - A Journey in Mob Programming

Transcript

1. A Journey in Mob Programming Joe Lloyd josephglloyd@gmail.com @joeywinsford
2. Hi, I’m Joe I joined Advanced Legal as a dev in April 2015 I had lots to learn! - Pair programming - TDD - Single-piece flow
3. A New Team Forms Andy the Lead Dev Me (hi) Steve Barry We are all keen to learn and improve!
4. Uneven Flow We try promiscuous pairing in a coding dojo Needs a lot of discipline! Beginner’s mind - does how we work affect the work we do? Problems with flow - slow lane tasks Team life is good, but can be better!
5. The Brown Bag ‘Mob Programming - A Whole Team Approach’ by Woody Zuill Available on Youtube and Vimeo Mechanics same as our coding dojos, where we focus on learning
6. Mob Programming “All the brilliant people Working at the same time In the same space At the same computer On the same thing” -- Woody Zuill
7. One Week Experiment Mob everything! See what works and what doesn’t We practice the mechanics and fine-tune for us Retro after one week
8. Mob Station One - our first setup
9. Making it work with what we have No kit needed! Share screens with Skype, Slack, Hangouts, etc.
10. This photo was completely staged Face-to-face More open More discussion
11. Share the Learning Andy the Expert with teammates new to XP? 1-to-1 teaching limited by teacher resources Group training impersonal and untargeted, not seen as ‘work’ Mobbing builds learning into team life Everyone learns facets - comes into a whole
12. Freedom! Freedom to come and go Pairing could be restrictive Key people can attend meetings without stopping work Spread the strain - everyone has bad days
13. Seeing Other People Specialists join the mob when needed - product, UX, etc. Integrate remote workers Tool of pref: WebEx > Lync > ScreenHero (Slack) >>> Hangouts Patient Zero can work with us from home!
14. Bring Down the Wall Tester works in the mob No more chucking it over the wall More eyes on quality at the right time More confidence done is done
15. Transform the Team “Kindness, consideration and respect” Lack of consensus is a smell Problem too big? Poorly understood? Useful data! Curb your enthusiasm - get ‘good enough’ No hiding! Regular retros - space, resolve conflict, respect
16. Mob Consciousness Your own faults are hardest to spot Everyone in team is responsible for discipline Practice what you’ve learnt by telling off the experts Better chance to catch problems early - are we doing the right thing? - in the right way?
17. Going Strong We still mob everything Mobbing has built great team alignment Values, practices, consistent codebase Created team charter to keep things strong
18. Q: What did you think when we started mobbing? “It sounds mental. It shouldn’t work, but can’t ignore the benefits from the video.” “I was highly skeptical. I’d only just bought into pairing - how can it scale to more than a pair without losing productivity?”
19. Q: How did your thoughts change? “It somehow works - not sure why! My initial guesses were more communication in the team, better single-piece flow.” “Immediately gobsmacked at how it fitted together. It brought the team together naturally.”
20. Q: What advice would you give others trying mobbing? “Be open-minded and give it a go. Be nice to people!” “Try it! Doesn’t sound like it should work, but it does!”
21. Thanks! Joe Lloyd josephglloyd@gmail.com @joeywinsford