[theboywho]

This is an example of when Daniel Kahneman said that people don’t believe in something because there are arguments but believe the arguments because they believe in something. Here’s why I think so:

> syncing plans and priorities for the current day

Most of the work developers do require syncing multiple times a day, either by slack messages, GitHub comments or pair programming, etc. Waiting for the daily to sync is not realistic and would waste tons of time.

> signaling blockers early so the team can help

If you have a blocker and you wait until the daily to mention it, you have a bigger problem. Blockers should be notified right away and most teams do this over slack or other messaging platforms they use.

> encouraging collaboration and knowledge sharing

Teams are usually small, and if you don’t already know what someone is doing, you wouldn’t care what they have to say during the daily, and if you care what they have to say, you already know what they are doing.

> building a sense of team ownership and support.

Just go for a coffee break.

If you believe daily standups are useful, chances are you’re actually part of the problem.

[scott_w]

> If you have a blocker and you wait until the daily to say it, you have a bigger problem. Blockers should be notified right away and most team do this over slack or other messaging platforms they use.

They should but it doesn’t always happen. Having a stand up makes sure you can get that information into the open.

This holds for literally everything. You shouldn’t hold back conversations for your 1-on-1 but, if you don’t have them, you’ll find there’s a load of conversations you miss out on that you needed to have.

[theboywho]

Having a daily standup might be encouraging people to wait until the daily to mention blockers, which could be harming your team all while you think it’s working