More Related Content
Similar to Pair Programming - Everything you need to know (20)
Pair Programming - Everything you need to know
- 2. Agenda • What is pair programming? • What are the roles in pair programming? • What are the benefits of pair programming? • What are the risks of pair programming? • Things to consider before starting pair programming
- 3. What is Pair Programming? • Two developers are working on the same taks at one workstation • Both have the same target • Both have different expertise • The roles are being switched on a regular basis • The two developers work as a team • Pair Programming is not mentoring even if one person is less experienced
- 4. What are the Roles in Pair Programming? • There are diffirent pairing options • Expert & Expert • Junior & Expert • New Colleague & Expert
- 5. The Driver & The Navigator • recommended for Expert & Expert pairing • THE DRIVER • Executes the task • Writes the code • Speaks out everything that he/she is doing • THE NAVIGATOR • Watches and observes • Corrects the driver if mistakes are made/ detected • Gives improvement suggestions • Makes sure they both stay on track and do not lose focus • Takes notes for things/ task to look into later
- 6. The Tourist & The Tourguide • recommended for New Colleague & Expert pairing • THE TOURGUIDE • „Guides“ the tourist and explains what he/ she is doing • Emphasizing the most important „highlights“ • Makes sure the tourist stays engaged by asking questions like „I would check it in like this, ok?“ • THE TOURIST • Listens to the touristguide • Rather passive participation, but needs to listen & pay attention actively • Asks questions if something is not clear or more details needed
- 7. The Driver & The Backseat Navigator • recommended for Junior & Expert pairing • THE DRIVER • Executes what the Backseat Navigator tells him/ her • THE BACKSEAT NAVIGATOR • Tells the driver what to do • Has to be able to articulate very well & precise
- 8. What are the benefits of Pair Programming? • Improved Code Quality • Continues Code Review • Less Defects -> defects are detected and removed early -> less bugs afterwards • Better Problem Solving -> solutions for problems are discussed on the spot & hopefully a solution is found • Shared Knowledge accross the company • Less exclusive „experts“, more compentecies and expanded skillset in the teams • Having a back-up if someone leaves/ gets sick
- 9. What are the benefits of Pair Programming? • Shared responsibility and shared „pressure“ • Ensures timely delivery • Less Distractions -> Higher Productivity • Team Building • Improved communication • Improved trust among team members • Better induction of new team members • Increased motivation
- 10. What are potential risks of Pair Programming? • Finding the „right“ partner • Do not pair people who do not like each other • Pair of two developers who do not know anything about the project and/or how to implement it • Scheduling problems • Early risers vs sleeping in types • Disagreements • Not respecting each other
- 11. Best Practices - Things to consider 1. 1x Code - 1x Computer – 2x Developers 2. Working Environment • On-site - > 1 computer -> good visibility of the monitor(s) for both; whiteboard or paperblock for ideas • Remote -> Screensharing; Webcam; Shared Chat for ideas/ notes 3. Agree on Pair Programming Parameters • Timing • Interval of changing roles • Breaks
- 12. Best Practices – Things to consider 4. Clearly defined & understood task • It is important that both know and work towards the same goal • Shared understanding on what needs/ will be done 5. One task at a time • The driver works on one task at a time -> focus • The navigator needs to keep track of it • Note down other things that have to be addressed for later 6. Switch the roles on a regular basis
- 13. Best Practices – Things to consider 7. Have patience and take breaks • Both partners will need to have patience and focus -> mental fatigue • Thus it is important to take breaks on a regular basis 8. Communication is everything • Communicating what the driver is doing and why • Carefully listen to one each other • „Synchronising“ the minds 9. Stay Focused • Close all unneccesary tabs and remove things that you do not need
- 14. Best Practices – Things to consider 10. Align your code • It is recommended that you agree on a common programming style 11. Do not look at Pair Programming as control or monitoring • It is collaborative development 12. Be Open • Both need to be open and bring a certain degree of cristicism and willingness to compromise • Be open to other/ alternative solutions and ideas 13. Know when not to do Pair Programming • Trivial Work • Research Work
- 15. The End.