Feature branching slows delivery

As well as causing merge conflicts, feature branches slow the delivery of new features.

Someone needs to be responsible for merging the branches once they've been reviewed and approved, and any further merges into release branches.

This is typically the Lead Developer on the project, but this person then becomes a bottleneck.

They need to oversee all the branches and merges, and know what needs to be merged and where it needs to be deployed.

This slows down the speed of delivery.

In a trunk-based environment, there's only one branch and everyone can commit and push to it.

And, if you're doing continuous delivery, any changes will be automatically deployed.

No more bottleneck.