MAD Trunk Based Development - A case study

I have done a survey of a team's experience of using Main-as-Default Trunk Based Development with Non-blocking reviews. What we found out is that teams don't need to adopt TDD, Pair Programming or o...

I have done a survey of a team’s experience of using Main-as-Default Trunk Based Development with Non-blocking reviews. What we found out is that teams don’t need to adopt TDD, Pair Programming or other similar QA-defensive mechanisms to adopt Trunk Based Development. Instead reducing friction, getting early feedback and delivering in small increments appears to create quality and robustness in itself.

I have written an article about it here: https://www.linkedin.com/pulse/wont-main-break-all-time-your-team-commit-straight-martin-mortensen-tkztf/

As well as other related articles: https://www.linkedin.com/in/martin-mortensen-sc/recent-activity/articles/

And you can see the Dave Farley take here: https://www.youtube.com/watch?v=CR3LP2n2dWw