• Solutions
    • I Can Help
      • Define
      • Educate
      • Integrate
      • Advise
    • Consultation
      • Assessments
      • Design Reviews
      • Code Inspections
      • Ongoing Support
    • Training Classes
      • Training Schedule
      • On-Site Classes
      • Online Training
      • Customized Coaching and Mob Facilitation
    • Learning Roadmap
      • Developer Essentials Training
        • Agile Analysis and Design Patterns
        • Hands-On: Extreme Programming Practices
      • Scrum Framework Developer Essentials
      • Design Pattern Developer Essentials
      • Object-Oriented Analysis and Design Patterns
      • Scrum Software Developer Essentials
      • Agile Software Developer Essentials
      • Agile Software Developer Intensives
    • Speaking
      • Beyond the Legacy Code Crisis
      • Five Developer Practices for Agile Software
      • Writing High Quality, CLEAN Code
      • Essential Scrum Developer Practices
      • Improving Your Scrum Process
      • The Agile Development Advantage
    • Testimonials
    • Clients
  • Resources
    • Blog
    • My Book: Beyond Legacy Code
    • Bibliography
    • Referral Program
    • Associates
  • Contact
    • Contact Me
    • Schedule A Call
    • About
  • Schedule A Call

Track Progress

  1. Home
  2. Blog
  3. Track Progress

2025 Public Training Schedule

June 23 26, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

July 22 – 25, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

Register Now
Or schedule a private class
Course Descriptions
  • Developer Essentials Training
    • Agile Analysis and Design Patterns
    • Hands-On: Extreme Programming Practices
  • Object-Oriented Analysis and Design Patterns
  • Scrum Software Developer Essentials
  • Agile Software Developer Essentials
  • Agile Software Developer Intensives
Follow me on Twitter:

Follow @ToBeAgile

Blog Post Categories
  • Announcements {19}
  • Articles {2}
  • Bits and Pieces {74}
  • Blogosphere {1}
  • Bonuses {2}
  • Build in Small Batches {27}
  • Collaborate {38}
  • Create CLEAN Code {34}
  • Implement the Design Last {11}
  • Integrate Continuously {30}
  • Off-Topic but Interesting {3}
  • Rants {82}
  • Refactor Legacy Code {24}
  • Say What, Why, and for Whom Before How {22}
  • Seven Strategies {38}
  • Specify Behaviors with Tests {17}
  • Write the Test First {27}
Archives
  • 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • 2022
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • 2021
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • 2020
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • 2019
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • 2018
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • 2017
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • 2016
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • 2015
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • 2014
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • 2013
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • 2012
  • December 2012
  • Privacy Policy

    (c) 2025 To Be Agile

    • August 7, 2019
    • Collaborate

    As the proverb says, “Data speaks louder than words.” Well, if it’s not a proverb then it should be.

    The only way to know for sure if pair programming is right for your team is to track progress and see if the metrics that are important to you improve as your team starts to become more collaborative with pairing.

    What are the metrics that are most important to you? When I look at pair programming, the most important indicator that I focus on is code quality. When I say code quality I mean several things. 

    The easy and quick way to interpret what I mean by code quality is to look at the testability of code. If developers are producing good, testable code that has automated unit tests and can independently verify each feature then I know I have a true measure of my progress and I have a good sense that high-quality code that’s straightforward to maintain and extend is being produced.

    For me, the number one metric that I look at is testability in code but there are other metrics that you can look at such as code coverage and cyclomatic complexity, as well as many other indicators.

    I also want to look at the amount of work that the team is doing but generally, I don’t like to track story points. Rather than assign tasks with different story points, I like to help teams get good at breaking tasks down into their smallest components so that every task is a small task and then instead of counting story points we simply count tasks.

    The number of tasks the team can complete within an iteration is likely to be similar to the number of tasks the team completed in the last iteration or the one before that. Generally, if the team isn’t trying to do something very different than they were doing before then one could expect that the team’s throughput would be similar to their past performance. 

    How much more precise do we need to be and how much are we willing to pay for that precision? Historically, we’ve been very bad at estimating how much work needs to be done, especially as the time horizon increases. Estimation can help with planning but an estimate is not a deliverable. I find that often managers are willing to pay far more than they should for an inaccurate estimate that didn’t make any difference on the project.

    I think that planning and estimation, especially the way it is practiced in Scrum, is largely a waste of time and can be inappropriately used by management as a way of forcing developers to get more done even at the expense of cutting corners and incurring technical debt. 

    Many of the ways that we track progress in software development actually de-incentivizes developers from doing the right things. If we are incentivized to make local optimizations but those local optimizations don’t affect the overall throughput, then the ultimate value of those optimizations is still very low.

    If your team spends a lot of time in triage fixing bugs then finding ways to prevent bugs from being created in the first place could hold a great deal of value. Traditionally, this is one of the benefits of pair programming.

    I find that for many tasks pair programming can be more efficient and effective but you can’t assume that two people will immediately get the work done together that they could have done by themselves in the short term because there is always a learning curve. It can take some time before two people get into enough of a groove to really get high productivity. But when it happens it can be magic.

    I like to look at before and after data, a lot and generally I look at things like defect rates before and after a practice is introduced. I also look at code coverage and cyclomatic complexity but just as indicators on code quality because I don’t think we can programmatically determine whether a piece of code is good or not, we have to examine it ourselves.

    Ultimately in my experience, I find exactly what the published studies find, which is that pair programming improves not only developer quality but also productivity. Fewer defects are being created, more requirements are being interpreted in ways that are of value to the customer and technical skills are being propagated throughout the team so that everyone’s collaborating more effectively and efficiently. 

    When I see teams who adopt Extreme Programming practices such as pair programming and the gains that they make over their competition I see how much of a competitive advantage high performing teams can be, especially in highly competitive and high-stakes markets.

    Note: This blog post is based on a section in my book, Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software called Seven Strategies for Seven Strategies for Agile Infrastructure.

    Previous Post: « Let Teams Decide on the Details

    Next Post: Why Practice 5: Create CLEAN Code »

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Solutions

    I Can Help
    • Define
    • Educate
    • Integrate
    • Advise

    Consultation
    • Assessments
    • Design Reviews
    • Code Inspections
    • Ongoing Support

    Testimonials Clients

    Resources

    • Blog
    • My Book: Beyond Legacy Code
    • Referral Program
    • Associates


    Read my book!
    Schedule a Call

    Training

    • Training Schedule
    • Learning Roadmap
    • On-Site Classes
    • Online Training
    • Customized Coaching and Mob Facilitation

    Course Descriptions
    • Developer Essentials Training
      • Agile Analysis and Design Patterns
      • Hands-On: Extreme Programming Practices
    • Object-Oriented Analysis and Design Patterns
    • Scrum Software Developer Essentials
    • Agile Software Developer Essentials
    • Agile Software Developer Intensives

    Copyright 2025 © To Be Agile. All rights reserved. Privacy Policy.

    This website uses cookies to improve your experience. I'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    SAVE & ACCEPT