> In what world when server is down people wait for the next standup to announce it?
I'm not sure why this is so strange to you. There are many possible scenarios where a server can be down, with varying levels of severity/impact to our team.
It happens all the time. I have 4 things to do. One of them involves a server (that we don't own). It goes down. I file a ticket and work on the other 3 things. It doesn't need to be resolved immediately. But if it isn't resolved in 2+ days, it may affect our timelines. People should know. If it got resolved in a few hours, I've wasted people's time by emailing them.
If it's critical and we need it resolved ASAP, sure - email/IM others in your team immediately to let them know.
> Why not just create a shared channel (slack, teams, mattermost, irc, whatever the company standardized on) and use it to communicate asynchronously and resolve problems like that immediately?
This was answered in my comment: People often ignore it. I can't count how often I've been in non-SUM teams where a developer is asked "Why didn't you tell us?" only to have him whip out one (or several) emails/IMs where he did tell it. Calling it out (repeatedly) in a SUM gives other developers less deniability, and the SM will highlight it: "This person has pointed out 3 days in a row. What's preventing it from being fixed?"
But the question for you: Are you always going to leave it to the individual developer to decide what is important to tell others? He may view it as unimportant whereas others believe it is. Making them explicitly say it as a blocker in a daily meeting ensures the disconnect doesn't last long.
I'm not sure why this is so strange to you. There are many possible scenarios where a server can be down, with varying levels of severity/impact to our team.
It happens all the time. I have 4 things to do. One of them involves a server (that we don't own). It goes down. I file a ticket and work on the other 3 things. It doesn't need to be resolved immediately. But if it isn't resolved in 2+ days, it may affect our timelines. People should know. If it got resolved in a few hours, I've wasted people's time by emailing them.
If it's critical and we need it resolved ASAP, sure - email/IM others in your team immediately to let them know.
> Why not just create a shared channel (slack, teams, mattermost, irc, whatever the company standardized on) and use it to communicate asynchronously and resolve problems like that immediately?
This was answered in my comment: People often ignore it. I can't count how often I've been in non-SUM teams where a developer is asked "Why didn't you tell us?" only to have him whip out one (or several) emails/IMs where he did tell it. Calling it out (repeatedly) in a SUM gives other developers less deniability, and the SM will highlight it: "This person has pointed out 3 days in a row. What's preventing it from being fixed?"
But the question for you: Are you always going to leave it to the individual developer to decide what is important to tell others? He may view it as unimportant whereas others believe it is. Making them explicitly say it as a blocker in a daily meeting ensures the disconnect doesn't last long.