The document discusses pairing in software development. It describes different pairing roles like driver and navigator and provides examples of how Sherlock Holmes and Dr. Watson exemplified these roles. The driver takes decisions, consults the navigator, and verbalizes actions while the navigator looks ahead, asks questions, and provides feedback without crossing the driver's comfort zone. Pair programming, testing, facilitation, talking and writing are presented as different ways of pairing with potential benefits like faster learning and higher quality products.
5. Driver
Takes the decisions
Consults with the Navigator
Focuses on short term actions
Verbalizes all the performed actions
www.mozaicworks.com
6. Navigator
Looks ahead for strategy
Annoyingly rechecks the facts of the Driver
Asks meaningful questions
Verbalizes agreement or disagreement
Does not cross the Driver's comfort zone
www.mozaicworks.com
10. Watson being a Navigator
“If I irritated him by a certain methodical
slowness in my mentality, that irritation
served only to make his own flamelike
intuitions and impressions flash up the
more vividly and swiftly”
Dr. Watson
www.mozaicworks.com
11. Watson navigating: Facts
The navigator remembers facts to the driver
The navigator supports driver's decisions
The navigator needs to see options ahead
Processing data is hard for navigation
www.mozaicworks.com
12. Holmes & Watson: Learning
“Education never ends, Watson. It is a
series of lessons, with the greatest for the
last.”
Sherlock Holmes
"I have not lived for years with Sherlock
Holmes for nothing."
Dr. Watson
www.mozaicworks.com
14. Holmes & Watson: Recap
Drive or Navigate
Observe well. Verbalize.
Give meaningful suggestions
Being a navigator is hard
Pairing is learning
www.mozaicworks.com
15. Some pairing ideas
Pair-programming (with testers also)
Pair-facilitation
Pair-talking
Pair-writing (collective text ownership)
www.mozaicworks.com
17. Pair-programming
Can be done anywhere: office, pub, etc
Change roles/keyboard very often
Outcomes: learning, better products
Fastest feedback cycle in Agile
Can be difficult
www.mozaicworks.com
18. Pair-testing
Focus on “destoying” the app
Find sneaky ways the system might crash
Change roles of driver and navigator
Outcomes: learning, better tests
Can be difficult as well
www.mozaicworks.com
20. Pair-facilitation
Can be done by anyone
Just ask someone to pair when facilitating
Outcome: learn better your skills
Outcome: be a better listener
Outcome: simplify&clarify your explanations
www.mozaicworks.com
21. Pair-talking
Fast feedback on content
Outcome: the talk has better content
Outcome: learn a lot from your pair
Outcome: you learn more from audience
www.mozaicworks.com
23. Pair-writing
Easier to start writing
The book can be finished faster
Fast feedback on content
Learning opportunity from your pair
www.mozaicworks.com
24. Pairing
Did I inspire you to pair?
What other ideas for paring do you have?
When would you start paring?
www.mozaicworks.com
25. And the last question
Do you ever pair with your CEO?
www.mozaicworks.com
26. Want to learn more?
Read more about pair-programming games
on http://blog.adrianbolboaca.ro
www.mozaicworks.com
27. Thank you!
The slides will be available on
Slideshare&Twitter
Questions?
www.mozaicworks.com