The worst part about the standup ritual is that no one talks outside standups.

With async text communication channels you'll post when an issue shows up. With the standups you'll wait until the next standup and maybe forget the details until then, or forget about the issue entirely and that will lead to technical debt.

> when an issue shows up

Advanced usage: post proactively before you reach the task/issue. This way people have time to comment on it and when you do get to it it's been clear what to do for 1-2 days.

▲

mystifyingpoi a day ago | parent | next [-]

> With async text communication channels you'll post when an issue shows up.

I do this all the time, but often no one cares about the issue I raised at that time. So I have to wait until next day standup anyway, because then I can raise the issue in group and force someone to comment or reply.

▲

maccard a day ago | parent | prev [-]

> With async text communication channels you'll post when an issue shows up

You clearly work with excellent teams who don’t need this then. My experience is that a large number of people, even competent people will not post when an issue shows up and will wait for however long until an update is asked of them and then say they couldn’t do it because they’re blocked.

▲

marcosdumay a day ago | parent | next [-]

That's caused by daily meetings, not a reason to have them.

	▲	maccard a day ago \| parent [-]
		I didn’t mention they’ll wait til the next daily update. They’ll wait until someone messages them on slack or pings them on jira/linear or the sprint planning

▲

nottorp a day ago | parent | prev [-]

I might be lucky. Or I might be avoiding large organizations on purpose. Most of the time at least.