I’m also fairly sure most organisations don’t do Agile right.
At least within my organisation, we do not design anything up front. We’re agile.
We don’t think about proper api modelling. We’re agile.
We also do barely any testing. We’re agile.
We do rewrite the UI a dozen times based on user feedback. After all, we’re agile.
Agile doesn't mean forgo design completely.
> We don’t think about proper api modelling. We’re agile.
See previous point.
> We also do barely any testing. We’re agile.
It's difficult, if not impossible, to be agile without testing. If you want to move fast, you want to be confident that your latest change didn't break anything.
> We do rewrite the UI a dozen times based on user feedback. After all, we’re agile.
Sounds like you built a complete UI before any users could give you feedback. That's the opposite of agile.
But in the name of agile, business tends to get away with a lot of bad decisions, at least in the places I’ve worked.
Is it all as bad as it sounds? No, but the times I’ve heard we’re not thinking about design upfront under the name of agile is staggering.
Also what I dislike about the agile way of working is that whenever somebody presents any argument against it, people always say “that’s not agile”. Great. But if it is how people DO agile, that argument is moot.
It’s like REST. Rest is great. But nobody (almost nobody) actually does Rest like described in the original whitepaper. We can’t just ignore the issues resulting from this discrepancy.