If in the course of one's work one becomes blocked, would one really wait until the following day's stand-up to tell anyone about this?
If so then I think both the worker and the company have bigger issues than whether the stand-up itself is a good use of time.
The mind boggles.
There is hard block and soft block. Hard block means you have no clue how to continue and so of course you should get help right away. Soft block means you have ideas and are working on it, but - unknown to you - someone else on the team knows exactly how to solve that problem and could solve it for you in a few minutes or you can spend all weeks working out the answer. The soft block is a lot more common - engineers are smart people who can solve complex problems, but we often fail to use the help of someone else who has already solved it. Thus the standup should be able airing problems that you just need to finish typing the solution in. Sometimes someone else will say "I can help you do this faster", others it is just keep working until you get it.
However 99% of the time what I see in Real Life is even when it's just devs talking they aren't offering up enough information for either of those to happen. Either imposter syndrome kicks in and they don't want to look stupid in front of their peers, or they're just annoyed at having a meeting. So it just becomes a status update meeting anyways
This to a T. An awful lot of stuff coulda gotten crushed, quickly, if I'd just asked for help ASAP instead of siting on it and feeling dumb.
edit: to be clear, I think they're good definitions, just never heard a definition
BS "can I pick your mind", chit/chat, questions that could be Googled, and of course, micromanagement BS are interruptions.
DSUs themselves are also interruptions -- it's just that they're scheduled and not event-based.
In other words, necessary communication is not interruption. Accidental communication is interruption (to be read as the same concept as necessary and accidental complexity).
Sometimes stand-up for me means 'remind myself what I was doing'; if not that then I've certainly not got far past it, haven't had long to get much done or be stuck. I'm unlikely to say in a stand-up that I'm stuck on something, I'll have a(nother) crack at it and perhaps ask after lunch if necessary.
https://www.scrum.org/resources/what-is-a-daily-scrum
From the horses mouth:
"The Daily Scrum is Not a Status Meeting"
Or maybe see about getting him certified.
They go around the room and everyone has to say something and it ends up being a status update.
The whole process becomes a micromanagers wet dream.
As long as you complete what's "agreed" to (which is transparently a conflict of interest: engineers stating what can be accomplished; the ones who have to do the actual work), then everyone seems bizarrely happy.
The reduced working hours I qualify as increased salary, which prevents me from jumping ship for a better salary. I also qualify the reduced work as metal health recompense for perpetually dealing with scrum narcissists.
It's Putts Law https://en.m.wikipedia.org/wiki/Putt%27s_Law_and_the_Success... - but somehow management's impotence is becoming increasingly transparent.
A lot of `Agile` material is just doublespeak meant to sell consulting hours and training.
kick them out.
"Hey you know your morning check in, this is the one true holy way that every company in the world should do it"
it's not even that it's not probably a good way to run stand-up. But the hubris is pretty extreme.
If this works for you then this is good.
But I think these meetings are not for devs or something is very wrong with the setup. If they are Devs are are in the same team and working on the same project then I assume they have access to version control => no need top update on what everyone is working one. Instead teach them to do small commits and to write better commit messages.
If the meeting purpose is to communicate what is blocking someone => this again fails IMO because then someone might wait 1 day blocked? And if they don't wait that much and do an action about it what is there to communicate about in a daily meeting?
Devs on their own could do that, and do it better, before such BS like DSU was invented...
It's for Devs only to make sure they are not blocked and they are communicating what they are working on. In my last company the non-tech people weren't allowed and the DSU was only for engineering.
It is not a daily status meeting!
If it has turned into this then it should be scrapped because as you say it'll lead to people leaving as they feel they are being treated as low skill staff.
Btw I wrote this in a DSU that had non-tech people yabbering and which was basically a daily status meeting.