Difficulty: Advanced
Estimated Time: 30 minutes

The primary objective of the "Trunk Based Development" module is to show you different branching models, and the principles and benefits of a specific branching model which is based on "trunk" (also known as master).

If you have not completed the Welcome module from stripe 2 nor the Version Control (VCS) module from stripe 1, you should do so before continuing with the TBD module.

By the end of the lesson, you should be able to:

  • Articulate the benefits of trunk based development against other models
  • Understand the principles of applying trunk based development
  • Adapt trunk based development practices in their own activities

Trunk based development

Step 1 of 7

The development model problematic

Dan and his team use GIT as version control system, as well as GitHub as repository and development platform.

When setting up the VCS, they chose a branching model which should work for them: short lived feature branches which they often commit to the trunk (master).

After some time, the team encounters some difficulties in implementing this model and therefore asks for Chun's expertise on this subject.


Chun DevOps coach engaged to help the Pet Clinic company and development team make the shift to a new way of working.
Paulo Product Owner for the Pet Clinic application
Santhosh Scrum Master who is facilitating the DevOps Kaizen events
Dan Developer working on the Pet Clinic application