Unlocking your team's potential with pair programming (workshop)
Download as pptx, pdf1 like385 views
The document discusses pair programming, which involves two people working together on the same machine, such as writing code, and describes the benefits as knowledge sharing, team resilience, better solutions, higher quality code, and easier team standards. It also outlines different pairing styles, practical considerations for pairing, advice for pairing, and when pairing may not be as useful.
More Related Content
What's hot (20)
Similar to Unlocking your team's potential with pair programming (workshop) (20)
More from Mattia Battiston (9)
![Agile metrics for predicting the future [2021]](https://cdn.slidesharecdn.com/ss_thumbnails/agilemetricsforpredictingthefuture-agileonthebeach-september2021-210902143845-thumbnail.jpg?width=560&fit=bounds)
![The Science of Happiness [OLD VERSION]](https://cdn.slidesharecdn.com/ss_thumbnails/thescienceofhappinessskytechconf-28apr2017-170502200302-thumbnail.jpg?width=560&fit=bounds)
![Metriche Kanban in pratica a Sky UK [ITA]](https://cdn.slidesharecdn.com/ss_thumbnails/metrichekanbaninpraticaaskyuk-07nov2015-iad15-151109124429-lva1-app6892-thumbnail.jpg?width=560&fit=bounds)
Recently uploaded (20)
Unlocking your team's potential with pair programming (workshop)
- 1. Unlocking your team’s potential with Pair Programming @BattistonMattia
- 2. About me ● From Verona, Italy ● SDM in Identity, since Oct ● Previously: Eng. Manager, Agile Coach, Software Crafter ● 6 years full time pair programming Mattia Battiston @BattistonMattia [email protected]
- 3. What is Pair Programming? 2 people working together (typically writing code) on the same machine
- 4. Benefits? ● Knowledge sharing Most Visible Even more powerful ● Team resilience ● Better solutions ● Higher quality ● More focus ● Easier team standards ● No code reviews ● Low WIP ● Better onboarding
- 5. Pairing Styles Driver/Navigator Driver completes small task at hand, talking through. Navigator focuses on bigger picture. Swap regularly Ping Pong P1 writes failing test. P2 makes it pass, then writes next failing test. P1 makes it pass, ... Strong Style "For an idea to go from your head into the computer it MUST go through someone else's hands" Fluid For experienced pairs, when balance of driving/navigating happens naturally
- 6. Practicalities ● 2 Keyboard + Mouse. 2 monitors (usually mirror). Be comfortable ● Common tools, shortcuts, setups, etc. ● Commit messages include names, e.g. “Mattia & Aram: JIRA-123 - blah blah …” ● Rotate every 1-3 days. Swarm on same story to maximise benefits ● IntelliJ: use “Presentation assistant” plugin to show shortcuts ● Remote pairing ○ https://screen.so ○ https://www.use-together.com ○ https://www.remotemobprogram ming.org
- 7. Advice ● Pairing is a skill to learn ○ It’s ok to not be good at it initially ● Everyone is different, need to learn how to pair with different people ○ Set ground rules before you start (how to disagree, taking breaks, approach, etc.) ● It’s tiring, but you do get used to it ● Be vulnerable. It’s ok to say “I don’t know”
- 8. When NOT to pair? ● Deliberate learning? Solve problems on your own for learning purpose (but not on production code) ● Easy tasks? Still useful to pair. Easy to not pay attention and make mistakes ● When you’re tired? Still useful to pair. That’s when we’re more likely to make mistakes ● Different skill levels? There’s something to learn from everyone. Running ideas past someone is always useful.
- 9. Resources ● On Pair Programming https://martinfowler.com/articles/on-pair- programming.html ● Strong style pairing http://llewellynfalco.blogspot.com/2014/06/llewellyns -strong-style-pairing.html ● Why I love Trunk Based Development (or pushing straight to master) https://medium.com/@mattia.battiston/why-i-love- trunk-based-development-641fcf0b94a0 ● Remote Mob Programming https://www.remotemobprogramming.org/
- 10. PRACTICE
- 11. Let’s practice! ● Setup: https://github.com/swkBerlin/kata-bootstraps ● Kata: http://codingdojo.org/kata/elephant-carpaccio/ ● Rules ○ 5 min Driver, 5 min Navigator ○ 10 min Ping Pong ○ 10 min Strong Style
- 12. Kata ● Accept 3 inputs from the user: ○ How many items ○ Price per item ○ 2-letter state code ● Output the total price. Give a discount based on the total price, add state tax based on the state and the discounted price.
Editor's Notes
- #3: Myself
- #5: Benefits Most visible one: Knowledge sharing Team resilience. Work never stops Better solution, as you talk about ideas with someone and end up with a better one (when it’s still early, not at code-review time) Higher Quality, bugs are caught as they are written More focus. Less distractions by email/phone/facebook/etc. Easier to enforce shared standards. Collective code ownership No code reviews. One step closer to trunk-based-development Easy onboarding Low WIP
- #10: http://llewellynfalco.blogspot.com/2014/06/llewellyns-strong-style-pairing.html https://medium.com/@mattia.battiston/why-i-love-trunk-based-development-641fcf0b94a0
- #11: A few teams are starting to use these metrics. But what about “when will this project be done?