A good start for sure would be to learn to listen and understand, not listen to answer.

This reminds me of my windows laptop asking me for my finger print, while me using two external monitors with a docking station and the laptop shut.

So TSMPFKaT? That’s catchy!

Management not admitting time estimates from dev, management not willing to understand dev estimates (to maybe find a smaller solution together) and/or dev committing to not reachable deadlines are not scrum problems.

This sounds like poor communication between dev and PO.

Who moderates it?

Correctly implemented its the exact opposite. But that seldomly happens, often due to management.

Scrum uncovers problems the organisation was not aware of before which is why it has such a bad reputation. „What do you mean I can’t push my feature requesting in to dev when ever I want? I thought we are agile?“

Oh I know many occasions to bring this up…

Reminds me of “If nobody knows what you are doing you’re not doing it wrong.”

I am curious. What do you carry in your pockets?

My wallet got exchanged by my watch. I grab my Smartphone only when I know I’ll need to get work done or take pictures when out and about.

Last thing are keys. But even they are narrowed down to front door, garage and bike. Sontheim other ones I only need at home.

I’d like to have that luxury as well!

While brushing my teeth I just spat out half of my toothpaste while reading this!

Said who?

UX in open source software is mostly fine for those who built it for them selves or people in the same environment.

As soon as stuff gets built for others with other requirements empathy declines, and I don’t mean this disrespectful. Good professional UX sources are needed, indeed to fill this gap. But will they be able to convince the open source devs who often were Initiator of the projects?