1. > When it is complex piece of work. It helps if one is analyzing, reviewing, and other is implementing (definition of ‘complex’ is contextual).
    > When one of the members is new in team.. it helps him to understand the coding style/guidelines, application working style etc

    This is very helpful, if certain piece of code can impact multiple flows or integration points. Pairing will result in better analysis and hence lesser impact on existing functionality.

  2. I think that’s good guidance for anyone. Risk, Complexity and Knowledge transfer are what I look for in the answer and you cover those bases very nicely. Thanks

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.