Pair programming is one of the important agile practices which is often compromised because of the cost. In this talk I will cover the importance of pairing and how is it not costly. There are many myths about pairing, most of th people think that they are pracitising pair programming but what they are actually doing is only the code review. In this talk I will also talk briefly about what is not pairing along with some secrets of effective pairing.

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. What is pairing?
  2. Perks of pairing.
  3. Myths about pairing.
  4. Effective pairs.
  5. Conclusion.

Learning Outcome

  1. Importance of pairing.
  2. What pairing is and what pairing is not?
  3. How to make pairing effective?

Target Audience

Developers, QA, BA, Project Managers, Scrum Masters

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jerry Rajamoney
    By Jerry Rajamoney  ~  3 years ago
    reply Reply

    Hi,

    Thanks for this topic. On seeing the outline of the topic I have the following query:

    - Are you going to talk Pairing from the concept perspective alone?

    - What about the view from Management and stakeholders on this?

    Thanks,

    • Tabassum
      By Tabassum  ~  3 years ago
      reply Reply

      I would talk about Pairig as a Concept and what are the benefits that we got on our project with it. I am also inclding how we followed pairing and how to make pairing more effective. So, in a nutshell talk would introduce the concept but with practical examples.

      First thing that Management or Stakeholders thinks about pairing is that it is expensive. But the benefits that you get are often ignored for example Quality, you don't have to invest in knowledge transfer, you don't create knowledge pockets, etc. This is the takeaway for the management, clients and other stake holders. Saying that pairing is expensive is like saying I don't want to go to gym because gym membership is costly but I am ok to have high cholesterol. Pairing must be costly in the development phase it is way cheaper than fixing a production.

      • Jerry Rajamoney
        By Jerry Rajamoney  ~  2 years ago
        reply Reply

        Hi,

        Thanks for the response. As mentioned, Will you be sharing some metrics / data to show the improvement of quality before and after pairing? Have you used any of these data / metrics to convince the management for adapting pairing?

        Thanks,

  • Pramod Sadalage
    By Pramod Sadalage  ~  3 years ago
    reply Reply

    Tabassum,

    Thanks for the proposal. I was wondering if you could list some of the myths and perks of pairing? are these myths and perks based on experience or research?

     

    Thanks

    • Tabassum
      By Tabassum  ~  3 years ago
      reply Reply

      Myths about pairing:-

       

      • one person implements and other reviews the code. 
      • two people distribute tasks among themselves and work individually.  
      • one person implements and explains the code and the other person listens. 

      Perks of Pairing:-

      • Code Quality
      • Individual Learning
      • Elimination of human errors
      • No Knowledge pockets created
      • Tabassum
        By Tabassum  ~  3 years ago
        reply Reply

        These are based on personal experience. Some of them learnings and trial and error.