> Really? There needs to be time set aside in the day for an engineer to announce that something is blocking their work? What were they doing for the rest of the day prior to the status meeting? Twiddling their thumbs? Office chair jousting tournament? When effective engineers get stuck, they ask for assistance immediately. Not tomorrow because PHB solicited that feedback. Immediately. Now.

I have seen standups actually induce that simply because there is an expectation that you did something yesterday. So how do you always ensure that you did something yesterday? You might withold reporting completed work.

There are some good points here on the futility of doing the "ritual" for the sake of doing the ritual. Especially when it comes to raising blockers - if you aren't attempting to resolve them when they come up, then are they even really blocking you?

But, I do think there is value in stand-ups for teams outside of a classic SE environment. I work on a team supporting a portfolio of related, but not necessarily interdependent analytics work. Stand-ups have proven valuable for us to look at ongoing work in the sprint, and identify deploy (shift) resources to individual stories that may need them. We're all in the same timezone, meeting virtually due to covid, and having a consistent meeting where we can talk through what we plan to do for the day has also opened doors for more informal collaboration than we had in prior formats. This may be the exception in implementation (or the "wrong way to do it") but we're trying to do what has value, and not just what's prescribed.