> On the other hand, I can be defensive too if people just want to rewrite software to change the implementation language. It always sounds fun at first until you grasp the complexity of the project again.
Yep, I'd agree with you here, fun new things for fun new things sake is usually a mistake. The cases I'm talking about though are where a slightly less commonly used pattern could actually drastically simplify the problem, but the other party is so set in their own mindset and way of doing things that they're unwilling to do it differently.
> In my experience these are use to give people outside of software (and some developers) an illusion of control.
Yes, perhaps that's it. The challenge is that in the last few jobs I've been in, the team themselves have also been in favor of these processes. The teams I've worked with seem to love just picking off tickets, having someone chop up work, and sitting in backlog grooming etc.