And that's how SAFe* was born :]
I've been a PO in a Scrum team for two years. It's the worst. No space to breathe, ever.
Unfortunately I think a lot of developers will see this as what "agile" actually means to them because it has been perverted so much.
Some companies have financial incentives to treat software as an asset - like a building that you build once and never change. So change is discouraged. You can make something once but fixing it is very much frowned upon as the cost has to go against the operational expenses budget. You can see how accountants think like this and how deeply it makes sense to them and yet how comically stupid it is.
I think the problem is everything is against agile development in a company which is not agile from the top and whose customers are not agile and which puts ridiculous financial reasons in front of those relating to the functioning of its products.
One of the things I absolutely love about my current job is not having to use agile. I didn't realize what a massive waste of time it was at my last two jobs because I'd never experienced not having to use it. If I switch jobs in the future, I'll definitely try and push management/product to try not using it.
Satire gets closer to the truth than truth does!
> Responding to change over following a plan
> provided a detailed plan is in place to respond to the change, and it is followed precisely
I worked for a company that went through an ISO 9001 process certification formalizing our Agile process. One of the charts detailed the process for changing the process. Art imitates life imitates art.
A CNAME to the agile manifesto?
> how those individuals (we prefer the term ‘resources’) interact
BCG uses the term ADU - Agile Delivery Units - instead of resources. That sounds directly like a term from the handbook of the ministry of truth.