[jseban]

Yeah which never happens in reality, as it's completely incompatible with a normal (risk averse) corporate environment. And the main premise is that there's recurring daily obstacles that the scrum master somehow can resolve, which never ever happens in reality. The daily is just an idea that never work out that way in reality.

[vannevar]

It does happen in reality. I've seen it many times, and it works.

[malermeister]

But why does anyone need a daily scheduled meeting for this? If I get blocked by something, I message the appropriate folks on slack immediately.

Why would I wait for some meeting the next morning?

[vannevar]

Why would I wait for some meeting the next morning?

You wouldn't. Why are you under the impression that scrum prohibits communication outside standup?

Daily scrum is a floor on communication, not a ceiling. It guarantees that focused communication happens at least once a day. Sometimes people miss slack posts and emails. Scrum makes sure the entire team is aware of progress and blockers. It's a tiny slice of the day when it's done properly.

[jseban]

Almost always the best way to solve an issue or a blocker, is for the person to simply continue to work on the task, alone. Very rarely is it productive to involve other people, and when it is, the person who is closest to this part of the work should be involved. To have a generic "issue solver" that solves everybody's issue is just not a good idea on a software team.

[vannevar]

Almost always the best way to solve an issue or a blocker, is for the person to simply continue to work on the task, alone.

No. There may be occasional cases where that's true, but it's almost always better to get another pair of eyes (and accompanying different experience) on a problem. There is some great software that comes from solo devs, but most commercial projects are simply too big for one person to accomplish in the time necessary. Business software is very much a team sport.