Member-only story
How to teach Trunk Based Development?
Small steps and timeboxing are key.
TBD
A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *, resist any pressure to create other long-lived development branches by employing documented techniques. They therefore avoid merge hell, do not break the build, and live happily ever after.
https://trunkbaseddevelopment.com/
When we are talking about what is Trunk Based Development (TBD), we define it as a practice done in the way explained above. But we don’t need to know how to do it, how to work in Trunk Based Development, how to practice?.
Some people don’t do it because they cannot imagine how to start, what is the simplest way to start doing TBD?
TBD works if you do small steps, without small steps it’s not going to work. So let’s focus on small steps.
The Kata
To start we are going to play a game inside the team, someone can prepare a Software Kata, for example the String Calculator or Mars Rover.
I prefer not very complicated Katas, because we are not interested in exploring how good we are solving problems, we are more interested in the mechanics we are going to put into place to learn TBD.
I would also suggest selecting Katas very focused on behaviors, not on technologies, we don’t want to…
