Book Image

Practical Remote Pair Programming

By : Adrian Bolboacă
Book Image

Practical Remote Pair Programming

By: Adrian Bolboacă

Overview of this book

Remote pair programming takes pair programming practices to the next level by allowing you and your team members to work effectively in distributed teams. This helps ensure that you continuously improve code quality, share equal ownership of the code, facilitate knowledge sharing, and reduce bugs in your code. If you want to adopt remote pair programming within your development team, this book is for you. Practical Remote Pair Programming takes you through various techniques and best practices for working with the wide variety of tools available for remote pair programming. You'll understand the significance of pair programming and how it can help improve communication within your team. As you advance, you’ll get to grips with different remote pair programming strategies and find out how to choose the most suitable style for your team and organization. The book will take you through the process of setting up video and audio tools, screen sharing tools, and the integrated development environment (IDE) for your remote pair programming setup. You'll also be able to enhance your remote pair programming experience with source control and remote access tools. By the end of this book, you'll have the confidence to drive the change of embracing remote pair programming in your organization and guide your peers to improve productivity while working remotely.
Table of Contents (14 chapters)
1
Section 1: Introduction to Pair Programming
5
Section 2: Remote Pair Programming
9
Section 3: Tools to Enhance Remote Pair Programming

Improving the restrospectives continuously

Retrospectives are just a part of continuous improvement, as retrospectives are a snapshot of your perception of the team's practices at any given moment. We need to further analyze the results of the retrospective, take the improvement actions seriously, and start seeing how each of us needs to change personally to improve the whole ecosystem. We cannot change the system without changing our personal behavior little by little. That is why, more than retrospectives, we should also look into a few more topics, all of which we will cover in this section.

Analyzing the results

As you started with a clear purpose in mind, you can check, after a while, if you are on the good path or not. Let's say you started with the purpose of minimizing the number of defects, and you started pair programming with that in mind.

Make sure all the data is available to the whole team. A good idea is that the whole team analyzes the data and...