Software developer since 1995, started programming in 1983 with Sinclair BASIC. Java developer since 1997, some JavaScript. Recent experience building Spring Boot REST services and some React.
Organizations need to encourage their people to question 'why are we doing this?' and ask whether it adds value. If it doesn't add value, why are you doing it? Similarly, the old joke about 'we have x people in this room for an hour, at $y/hour this meeting is costing us (and most likely the client) $x*y - is this meeting worth it?' - this needs to be asked seriously as a sanity check for avoiding unnecessary meetings, or exchanges of info that can be done in seconds via an email or Slack, verses having everyone held hostage in a room for an hour.
15 min standups are more efficient than many other traditional status meetings in the past (if you keep them timeboxed), but if the information being shared is not useful, why do it? If the opportunity for team members to ask for help when they're blocked is the most valuable part of a standup, you don't need the whole team in a room to enable this?
Kevin - exactly. I've have actually done that calculation in my head when in large unnecessary meetings at previous companies.
I think you're right that blockers that are dependencies are better handled through slack. Mostly because you can get things moving sooner.
For technical blockers, I think it is useful to talk about it as a group sometimes. Everyone on the team has a different background and maybe someone has already tackled this. Still possible on Slack, but I think better solutions can sometimes be landed on through conversation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Organizations need to encourage their people to question 'why are we doing this?' and ask whether it adds value. If it doesn't add value, why are you doing it? Similarly, the old joke about 'we have x people in this room for an hour, at $y/hour this meeting is costing us (and most likely the client) $x*y - is this meeting worth it?' - this needs to be asked seriously as a sanity check for avoiding unnecessary meetings, or exchanges of info that can be done in seconds via an email or Slack, verses having everyone held hostage in a room for an hour.
15 min standups are more efficient than many other traditional status meetings in the past (if you keep them timeboxed), but if the information being shared is not useful, why do it? If the opportunity for team members to ask for help when they're blocked is the most valuable part of a standup, you don't need the whole team in a room to enable this?
Kevin - exactly. I've have actually done that calculation in my head when in large unnecessary meetings at previous companies.
I think you're right that blockers that are dependencies are better handled through slack. Mostly because you can get things moving sooner.
For technical blockers, I think it is useful to talk about it as a group sometimes. Everyone on the team has a different background and maybe someone has already tackled this. Still possible on Slack, but I think better solutions can sometimes be landed on through conversation.