• 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

Commit Frequently

  1. Home
  2. Blog
  3. Commit Frequently

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

    • February 28, 2018
    • Integrate Continuously

    One metric that I think is most important to look at during an Agile transformation is the frequency of commits that developers make due to the build.

    This gives us a huge amount of information about several important things. First and foremost, it indicates the amount of friction in the build and how much work developers have to go through in order to commit their code. For example, without a set of automated regression tests committing our code requires a manual testing process that is often deferred to the end of the iteration, or even to the end of a release. This might make a lot of sense in building construction, but it’s highly inefficient when constructing software.

    Building software requires many parallel tasks, but it’s far more efficient to take a task start to finish without interruption, and finding a balance between what to do now and what to defer on is very important.

    To me, this speaks to the very essence of Agile, which is all about delivering working software. In Scrum, at the end of every sprint we’re supposed to have working software, not software we hand off to QA for testing.

    When we separate development and test, we can introduce major inefficiencies to our system, and we’re also interrupting the flow of development, forcing developers to go back later to fix mistakes and incur massive time delays to reacquaint themselves with code that they wrote just a few days or weeks earlier.

    This is what I call Painful Agile and I see many teams doing Painful Agile. Committing every two weeks is less painful than committing every three months, which is less painful than committing every year, but all of these commitment intervals include some degree of pain.

    The pain only really goes away when we are committing all the time, whenever we have any little bit of functionality to add to the system. When we can commit frequently, we get working software more frequently as well, which lets us to validate that we’re on track more frequently and gives us a true measure of our progress.

    Committing frequently also means that developers are breaking down stories into small, manageable tasks, which has innumerable benefits for Agile development. It not only shows us that our build has low friction so it’s straightforward to use, it also shows us that developers are good at breaking down stories into manageable tasks, which is another set of skills that are very important for an effective Agile development cycle.

    In a healthy development environment, we commit several times a day. This may not mean that were writing several features a day but rather that we’re good at breaking out features into manageable chunks and each one is a step in the direction of overall progress.

    And when we commit to version control, we are committing to trunk. The whole purpose of committing frequently is to let our newly developed code coexist with the rest of the system. This is what continuous integration is all about, but it can easily be defeated through branching.

    I know lots of teams who use version control but each developer works in their own branch and it’s only much later, right before release, that the developers integrate their feature branches back into truck. There is a name for this approach and it’s called Waterfall.

    Building software in feature branches really defeats the purpose of version control in the first place. Long live branches may seem like they are a good idea but they are almost always an anti-pattern because it isolates code rather than integrating it.

    We want newly integrated code to be part of the whole system so we can validate that it doesn’t affect any other part of the system. Integration is traditionally when the worst bugs show up. When we put off integration we’re basically keeping ourselves from seeing the truth of our build and if we don’t know about problems we can’t fix them. When we integrate toward the end of a release, we can learn about problems and bugs when it’s too late to do anything about them.

    But when we commit frequently we can see a true measure of our progress and the problem space is fresh in our heads, so if we discover a bug we can typically fix it right away. This has one of the largest boosts to productivity that we can get in software development.

    Previous Post: « Keep Defects from Escaping

    Next Post: Thinking with Objects »

    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