Trunk-Based Development Under Scrutiny: Is It Worth the Hype?

Trunk-based development (TBD) is a key practice in software engineering where developers consistently merge their work into a single branch, or “trunk”. This method aims to streamline collaboration and accelerate integration. However, the 2022 State of DevOps Report presented a conundrum, suggesting TBD might not always enhance team performance and might be challenging without seasoned professionals.

Dr. Nicole Forsgren highlighted the complexity of these findings, signaling that the connection between TBD and high organizational performance could be misinterpreted or coincidental. Her insights warranted a reexamination of the application of TBD.

In the 2023 report, we see a nuanced perspective. It's indicated that TBD, when paired with the following practices, can indeed elevate organizational performance:

1. Prompt, detailed code reviews
2. Consistent integration practices
3. Comprehensive documentation

Despite these insights, TBD is not universally applicable. Here are some cases where it might not fit:

1. Teams without experienced developers: Without experts in TBD, the team might struggle to keep up with frequent updates.
2. Strictly regulated areas: In places where there are numerous compliance rules to follow, TBD’s quick changes might be too hard to manage.
3. Open-source work: Projects with many external contributors might not be able to use TBD well because it needs close teamwork and fast updates.

It's crucial to understand that pushing practices alone to complex sociotechnical systems without a mindset changes are doomed to failure. You need to work on both technical and cultural aspects to successfully introduce changes in your system. As the 2023 DevOps report shows, trunk-based development needs to be accompanied by other practices to create an ecosystem where it increases the organizational performance.

Dave Farley, a proponent of Continuous Delivery, has offered his reflections, noting his surprise that TBD and continuous integration (CI) did not show a more substantial impact on software delivery performance. Farley considers CI foundational, essential for understanding and verifying software stability and throughput. His musings suggest that if CI is the measure of delivery performance, its subtle influences may require deeper exploration beyond initial interpretations.

To adopt trunk-based development in your team, I recommend following Ivan Badia Morales ' guidelines in his most recent talk at the Software Crafters Barcelona ?? :

1. Start building high trust in your team.
2. Identify waste and waiting times.
3. Limit your Work in progress (WIP).
4. Accelerate your flow speed with asynchronous communication.
5. Adopt pair-programming or mob programming to increase confidence in your team.
6. Work on having “Smart Endpoints and Dumb Pipes”.

Ultimately, the journey from the 2022 report’s cautious stance to the 2023 report’s refined understanding of TBD affirms that the success of such practices lies not only in their implementation but also in the supporting ecosystem. It's a complex interplay between methodologies, comprehensive practices, and the collective skill of the team.

Embrace the learning curve, and let's forge pathways to not just resilient software, but also to adaptive and robust teams.

Have you integrated trunk-based development into your workflow? We're curious to hear about your on-the-ground experiences. Whether it’s been a game-changer or a challenge, your stories enrich the conversation. Join us in the comments to share your journey with TBD — the triumphs, the setbacks, and everything in-between. Your insights could be the beacon that guides others in this evolving landscape of software development practices.

#DevOps #TrunkBasedDevelopment #ContinuousDelivery #SoftwareEngineering