But, in practice, I'd prefer somebody gave a little more context than a simple "working on X" (assuming X isn't trivial - if it was, you would have finished it already) - what part of X... Design? Coding? Testing? Any roadblocks? Do you expect to turn it over to QA today or tomorrow? Nobody is working a vacuum and all our work intersects at some point.
Assigning turns so that someone is forced to spit out that gibberish is nonsensical. Allowing someone the floor when they speak up when they have something to say is worthwhile, and something people do naturally. There is no need for an explicit turn where someone must say something.
> Regurgitating a, what is little more than gibberish, canned response when you have nothing to say is very different to speaking when you have something of value to say. That it only takes 10 seconds to utter that gibberish does not give it any more value.
I can't tell if there are two people on your account? Maybe you two should chat.
They technically could, but usually they are smart enough to realize that it is stupid to do so and reserve the act for when they know they have something of value to contribute.
If you are hiring stupid people, well, good luck. Someone uttering gibberish is likely the least of your worries, which no doubt explains why you haven't noticed the problem with it.
I never mentioned a canned response they were told to say. You've invented this.
That you seem confused about the subject now is... strange.
Sure, you can say that in 10 seconds. More likely even less time. That doesn't mean you should. It provides nothing of value. Setting a specific turn aside so that someone has to say something useless is even crazier.
People don't say things because they're in a book. If you want to work as a team and quickly update your team on what you're doing, then leaving your day free to do or collaborate as needed, it's an efficient way to do it.
You don't (seem to) say all this should not be communicated, nor that the team shouldn't be aware of it. You seem to only be concerned with the form of the communication; that it should be implied where possible, and where it must be explicit, should be done in point to point conversations throughout the day. That seems a) worse and b) bikeshedding.
There has been no mention of the topic of blockers in this thread at all, save my last comment. I am not sure where you dreamed up the idea it was central to the discussion, let alone a part of it in any capacity.
> People don't say things because they're in a book.
Not on their own accord. If there is social pressure, or even economic pressure, to take a turn they absolutely do. This topic is not based on a work of fiction. It was a tale about someone's actual experience. One many have had at that.
You must have hit the wrong reply button somewhere along the way.
> It's not best to skip saying ten words that explain you're fine. It takes 10 seconds.
And you replying saying it's as bad as saying I was working on X; I will work on Y.
So, pretty clear I think.
If it gets said at all, you should also agree. If the goal if your standup is simply to hear people talk, talk about what you did on the weekend instead. That will actually provide value to the team in building a better relationship with teammates. "I did X yesterday, I will do X today" provides no information potential or bonding potential. It is flat out worthless.
More realistically, if all you have to say is "I did X yesterday, I will do X today" it is best to not say anything at all. The goal shouldn't be to hear someone speak, but rather to achieve a business objective. Sometimes people won't have anything to contribute towards that objective and that's okay. Other times they will. They can speak then.
Team meetings can be beneficial. Having the team meet so that they can utter practically-gibberish canned messages to each other is not beneficial. On the bright side, I see (from the parent comment and many others) that we have finally dropped the equally useless "no blockers" routine. We're making progress here!