News for hackers. Stuff that matters.
Re:Zoom Is Not the Problem – Our Meeting-Centric Workflow Is by ogre_codes on Thursday April 09, 2020 @09:03PM (#22828888)
At my current job, It's where pretty much all information about our project gets disseminated so without it, we'd be feeling around blind. Any priority changes; changes which might not be well defined in the wires or stories; deadlines; information about meetings with the clients. It's also the place where the dev team, design, and QA touch base so if an issue comes up where there are pieces missing in the wires or QA is struggling to test something, we can quickly bring it up.

A big chunk is actually most useful for the PM, but often enough other issues get addressed that our short status meetings don't bother me.

Re:Zoom Is Not the Problem – Our Meeting-Centric Workflow Is by nathanaldensr on Thursday April 09, 2020 @10:07PM (#22829254)
Asynchronous communication--Slack, Discord, Teams, etc.--beats this every time. Why wait an entire day to bring up important topics? And then, if you aren't waiting an entire day, why have the artificial morning ceremony?
Re:Zoom Is Not the Problem – Our Meeting-Centric Workflow Is by ogre_codes on Friday April 10, 2020 @03:45PM (#22836659)
I love chat rooms, but they are their own kind of interruption and you can often communicate more in 2 minutes of conversation than in 45 minutes of back and forth on slack. And again, there are benefits to knowing when important things are going to be discussed and planning around that rather than have them happen at random in Slack.