Comments by "Michael Stover" (@michaelrstover) on "Continuous Integration vs Feature Branch Workflow" video.

@krokeman I tried to get my team to go for an approach like that, but they wouldn't go for it, so it's branch-by-jira :-(
2
As I understand from other Dave Farley content I've consumed, the main answer is that Pair Programming counts as Code Review, and he points out that places he's worked with that had heavy requirements for Code Review due to things like SOX rules accepted Pair Programming as satisfying those requirements.
1
Personally, when the scenario you describes remains as you describe, it is generally good enough. It's when discipline wanes and the features that aren't yet done start sticking around in multiple branches that live for 3, 4, 5 days, and then weeks, and then months.... that's where it really goes terribly wrong.
1
@jimihenrik11 Branch-by-Jira is also what we do, but it does still lead to quite a few branches becoming quite long lived, and the delays between creating the PR and it getting reviewed and merged are super frustrating to me, and create a ton of inefficient context-switching. But, alas, I also failed to convince my management of the advantage of trunk-based development (and I'm the oldest member of the team!).
1