The daily standup comes from XP, which has no real concept of project managers or team leaders. Under XP, everyone is considered to be the project manager and team leader, so to speak. Thus, that isn't technically possible in the strictest sense.

If you have a "standup" in name only for the benefit of distinct project managers and/or team leaders, then I suppose you can just not show up. If that raises alarm in the organization, you're the newbie and just don't realize it.

What's important are blockers like inability to implement something, missing permissions, awaiting external communication, freshly detected requirements that need a decision, absences etc pp

Oh, in that case one should definitely wait 23 hours to bring that to anyone's attention, and for sure an (allegedly) 15 minute meeting is a great place to get requirements

> absences

Uh-huh, go ahead and include births and puppy adoptions, too; I can see that you and the Certified Scrum Master™ have obviously attended the same workshops on Team Health

Or at least, that's how it should be. But half the people tell long shaggy dog stories because they fear "I worked on feature X, it's going well" or some such is too short or basic, but it's not. Or they turn into long protracted debug sessions that's only really of interest to two people but 7 others are watching. That should be done after the standup.

It's really just intended to 1) give everyone a basic idea of what people are working on, and 2) a moment to check in and ask for help, and/or offer help.

But when was the last time you saw a team without managers? When you have managers, the whole reason for their existence is to take that kind of management work off the plate of developers, so that the developers can focus on what's important.

If you are having standups and managers, you need to seriously consider replacing the managers because they have straight up failed to do their job.

If one wants a status report, fine, have one periodically. But don't vaporize 30 minutes a day times 7 people just to go around the room talking. What a 1950s concept holy shit

I have never in my life met a professional who sits on their hands for 23 hours waiting to say "uh, I have a blocker, but wanted to save it for this magic 15 minutes to ask for help." Yes, fine, n00bs do that, and that's what TFA was saying that interns need supervision, who knew.

I will if there is a regularly scheduled meeting to discuss such matters. If the company is fine with you taking the day off, take it!

And yeah, I also can't agree more with your assessment about status reports being this relic from the past. What is this? The military? "SITREP. NOW!" Such a waste of breath, time, human life.

I feel we should separate these two things into async slack status reports and them regularly maybe bi weekly 30 minute team building meetings where no work is being talked about.

How did we get to the point where we determined that the only way to get anything out of developers was to setup a meeting to force it out? Telling them they must provide a status update on Slack instead is ultimately just a different cartoon character on the same basic bandaid – What is the actual problem here?

But I mean with respect to managers. The collaboration with them used to be exciting. What changed?

Then I draw one's attention to the rss feed of commit logs[1], unless you're expecting to get access to the Falcon console to watch what they're typing and visiting in their browsers, too

1: e.g. https://github.com/LuaJIT/LuaJIT/commits/master.atom and https://gitlab.com/gitlab-org/gitlab/-/commits/master.atom