Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

of

Pair programming Slide 1 Pair programming Slide 2 Pair programming Slide 3 Pair programming Slide 4 Pair programming Slide 5 Pair programming Slide 6 Pair programming Slide 7 Pair programming Slide 8 Pair programming Slide 9 Pair programming Slide 10
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

1 Like

Share

Download to read offline

Pair programming

Download to read offline

Pair programming explanation and some advises about how to success doing it.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Pair programming

  1. 1. Pair programming
  2. 2. Benefits ● Less bugs. ● Better code quality. ● Spreads business knowledge in the team. ● Creates a learning environment. ● Improves communication.
  3. 3. We should pair when... ● Complex features. ● Critical features. ● Core libraries. ● New part of the system. ● The team has a new member.
  4. 4. We should not pair when... ● One person is sick. ● Spiking code. ● Trivial tasks that don’t add value. ● The other person do not agree to pair.
  5. 5. Some techniques ● Driver - Navigator ● Ping - Pong
  6. 6. Driver - Navigator ● Driver: ○ Is the person typing the code. ● Navigator: ○ Helps driver. ○ Reviews what the driver is writing. ○ Keeps in mind the whole picture. ● Benefits: ○ Makes sure everybody is contributing.
  7. 7. Ping - Pong ● Driver: ○ Writes code. ● Navigator: ○ Writes the tests. ● Benefits: ○ Another developer evaluates functionality. ○ Learn about Test Driven Development (write the tests before the production code).
  8. 8. Some tips... ● Keep personal space. ● Clean desktop environment. ● The developers should be at the same distance from the monitor/s. ● Know the goals. ● Set timing, 4-6 hours per day. ● Change the roles frequently, at least once an hour. ● Rotate team members.
  9. 9. More tips… ● Pair programming is a negotiation. ● If you are bored pass the keyboard. ● If your partner is bored grab the keyboard. ● If both are bored, take a break. ● Talk a lot, this is about communication. ● If you do not understand what your partner is saying or doing, just ask.
  10. 10. Extra tip... 10-seconds rule The navigator should wait 10 seconds before pointing out a typo. Generally that is long enough for the driver to correct a typo that is already noticed. Excessive interruptions are distracting.
  • GarrisonLowe

    Jun. 9, 2021

Pair programming explanation and some advises about how to success doing it.

Views

Total views

55

On Slideshare

0

From embeds

0

Number of embeds

1

Actions

Downloads

6

Shares

0

Comments

0

Likes

1

×