But to indulge you, here's what scrum.org says, in part:
If you are just getting started, think of Scrum as a way to get work done as a team in small pieces at a time, with continuous experimentation and feedback loops along the way to learn and improve as you go.
Continuous experimentation, adapting with feedback, and learning and improving as you go? That doesn't sound like "process over people" to me.
Note also that the Agile Manifesto never says anything about not having some process. I think almost everybody would agree that a certain amount of process for the sake of consistency is a Good Thing. The problem is when people over-elevate the process to where it's seen as its own end unto itself, rather than a tool to help the team deliver the $THING they are trying to deliver.
But being "Scrum.org certified PSM", how do you see your colleague from scrumalliance.org?
Like renewable energy? 1st quarter 2024: 58,4% electricity from renewable energy. Up from 48.5% last year.
> Like renewable energy? 1st quarter 2024: 58,4% electricity from renewable energy. Up from 48.5% last year.
Generation, not consumption* (but still great!!)
Why people can't search for an existing term before creating a new one, it just add confusion into bucket which already contains "DB as API", "DB over API", "DB 2 API", "DB 2 REST", "DB low-code API"
This is another one.
There is no place in any professional field where you get away with poor choices.
Why call it a rocket stage ? Why not just call it exactly what it is - very bad judgement, very poor understanding and simply immature pop cultural choices.
No one in the right professional mind are making such choices. It might happen other places. But not in a professional setting.
But if it does get rid of those people. They are not good enough.