Several years ago right about when Extreme Programming (XP) became popular, one of the developers on a team I was managing wanted to give pair programming a try. He paired up with another programmer and went to work on some of our more complicated algorithms. I can’t tell you today whether that pair produced better quality code or if they were more productive, but they certainly felt proud of their achievements. So much so that they tried to influence other team members to give it a shot.That didn’t work over so well. The other developers in the group didn’t want to pair up and some claimed that it created an uncomfortable working environment.Today pair programming is a bit more accepted and understood, but I’m still not convinced it provides value in all development tasks and for all teams. I think pair programming is very appropriate when bringing new team members into a group as a form of training. It may also be useful in complex refactoring exercises, programming efforts that require significant object oriented designs, or development work on algorithms or procedures that have performance considerations. I’m sure there are many other tasks where there is a strong argument for pair programming.

But there is a danger if a team adopts it as a standard, default practice. In every development cycle, there comes a point where the team is challenged to take on more tasks either to meet a deadline, react to market conditions, or handle risks. At that point, the team may be challenged to break pairs in order to take on more work.

I know what some of you are saying. Breaking pairs doesn’t necessarily mean more tasks can be completed, and there is a risk that breaking pairs will reduce code quality or create more defects.

That said, I think a healthier approach is to budget for pair programming. Consider the following approach:

1. Given an iteration, one pairing team is established, what critical tasks would be assigned to that team?
2. Then look at the remaining tasks and decide which of them could be addressed using a single developer and introduce the least risk. Assign these tasks to individual developers.
3. Repeat this exercise until all tasks are assigned.
4. Look at tasks assigned to individual developers (non-pairs) and evaluate the aggregate risk. Consider other options to derisk including code reviews and additional testing.
5. After the iteration completes, the team should reflect on overall quality. Tasks where pair programming was applied, determine what benefits were realized. Quantify (or at least qualify) these benefits. For single developer tasks, quantify/qualify risks realized. Catalog this reflection.
6. Consolidate (5) into lessons learned. Apply these lessons to subsequent iterations.

By following this approach, a team can formulate a more scientific and defendable position on when to apply pair programming.

Published on:

Leave a Reply


StarCIO

My company, StarCIO, provides leadership, learning, and advisory programs for companies looking to accelerate delivering business value from digital transformation. Contact me if you’d like to learn more about partnering opportunities.


Isaac Sacolick

Greetings from Isaac Sacolick

If you enjoy my thought leadership, please sign up for the Driving Digital Newsletter and read all about my transformation stories in Digital Trailblazer.


Coffee with Digital Trailblazers hosted by Isaac Sacolick

Digital Trailblazers! Join us Fridays at 11am ET for a live audio discussion on digital transformation topics:  innovation, product management, agile, DevOps, data governance, and more!


Join the Community of StarCIO Digital Trailblazers

1 comment:

  1. I completely agree with you. I really like this article. It contains a lot of useful information. I can set up my new idea from this post. It gives in depth information. Thanks for this valuable information.

Drive: Agile, Innovation, and Transformation has 800+ articles on AI and digital transformation for leaders. Written by StarCIO Digital Trailblazer Isaac Sacolick. Learn more.


Coffee with Digital Trailblazers

StarCIO Coffee With Digital Trailblazers

Coffee With Digital Trailblazers is a weekly event for Digital Transformation leaders where we discuss leadership, delivering value from AI/data, and driving innovation.


About the StarCIO Digital Trailblazer Community

StarCIO Digital Trailblazer Community

Revolutionizing traditional learning, networking, and advising experiences.

Visit the community


About StarCIO

StarCIO: AI is reshaping business. Develop the leaders who can drive the transformation.

About Isaac Sacolick

Isaac Sacolick

Author, 1,200+ articles, keynote speaker, Chief StarCIO Digital Trailblazer. Full bio


Driving Digital Newsletter

Driving Digital Newsletter

StarCIO Guides

Learn StarCIO Agile Planning

Digital Trailblazer

Digital Trailblazer by Isaac Sacolick

Driving Digital

Driving Digital by Isaac Sacolick

Driving Digital Standup

Driving Digital Standup

Recognition

reworked imapct awards 2026 Judge
InfoWorld 2025 Judge
InfoWorld Technology of the Year 2024 Judge
Thinkers360 Top 10 in IT Leadership
Thinkers360 Top Agile Thought Leader
Thinkers360 Top DevOps Leader
Thinkers360 Top in Digital Transfomation
Thinkers360 Top in Analytics
Thinkers360 Top in Product Management