26 ms·
I'm not against collaboration or communication. On the contrary I think it's critical to well functioning and productive teams. I just think stand ups as I've
by JamesBarney 7y ago
I'm not against collaboration or communication. On the contrary I think it's critical to well functioning and productive teams.
I just think stand ups as I've experienced over 10 teams and 5 organizations haven't been especially useful. They have been a status update mostly for the pm and a little for the tech lead.
What is an example of helpful information you guys are sharing in your stand ups?
- ogre_codes 7y agoAt 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.
- nathanaldensr 7y agoAsynchronous 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?
- ogre_codes 7y agoI 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.