As humans, our natural pattern matching abilities sometimes causes us to see things that aren't really there. It's a blind spot for us.

In this particular case, you now have research that backs up our understanding of software development waste. If you read the paper, you'll see examples of how our previous understanding of software development waste was flawed: https://www.researchgate.net/publication/313360479_Software_...

It might be "common sense", but that doesn't even mean that it's not possible for competent and well-meaning people to fall into these traps when working in larger groups.

If any of this was common sense, it wouldn't happen so often.

Many things are much easier said than done, "create good architecture", "eliminate technical debt" etc. You can't just schedule X hours and then be done after X hours, and often the time you spent just made things worse. People have to realize that writing good code is an artform and not something you can just decide to do.

That, e.g., doing the same thing over wastes time is obvious. I don't need a taxonomy to tell me that. In my experience the cause of those things "happening" is that most people don't put much thought in what they are doing and why they are doing it. Programmers feel an "itch" to start coding when its not even clear what should be done. A gamble on one's intuition rather than a structured working procedure.

Don't overestimate our competence

Common sense isn't really all that common.