[rgblambda]

To be fair, if you've seen a senior team member write a badly worded Jira ticket containing a large amount of possibly unnecessary work, then foist it upon a junior (Or just describe what the want in a call and let the junior write it) because they knew it wouldn't stand up to scrutiny in Backlog Refinement, you would be a bit more in favour of that rule.

[hibikir]

If you have malicious senior developers that foist work on people that would never be approved when the full team is there, your problem is not using one methodology or another: your problem is in hiring and firing.

It's one thing to have checks on other people's work to deal with honest mistakes as quality control. A system set up to show that you mistrust the decision making of your senior workers is making it clear efficiency is never the goal. If I can't trust a senior to make sure a junior is doing well, they ain't senior.

[ljm]

That kind of behaviour might only present after a long tenure at the organisation, once such an engineer sees themselves at the top of the pecking order.

At which point, it boils down to how willing an organisation is to fire someone for going rogue, or whether it’ll close ranks around the senior engineer for whatever reason/excuse and fire the junior.