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.

I basically have nearly everything within home assistant showing up in HomeKit and never had issues so far. Home assistant is the player in the background running all the automations while exposing the most important devices to HomeKit (esp. for voice commands with Siri) Only downside using HomeKit as the „UI“: Notifications are very limited.

Smaller steps. One at a time. Test.

I started off with HA, integrating all my devices i had at once, totally enthusiastic as I was. There were times where I installed several automations and integrations within just a few minutes, not giving them time to work for them selves, especially not in a „productive“ environment with wife, kids, neighbours, etc. all involved in the system.

Lots of automations broke or did not work as expected and I saw my self confronted fixing so many building sites at once.

I am through the roughest part. But should I start from scratch any time I will most surely start I’d small, test, iterate and move on.

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…