5 ms·
100%. And don‘t forget about the useless standup meetings which are nothing more than a complete waste of time.
by HellDunkel 3y ago
100%. And don‘t forget about the useless standup meetings which are nothing more than a complete waste of time.
- arkey 3y agoWhy do you think standup meetings are useless? Maybe they are not run properly? I find them to be a pillar of our workday, within our team.
- miyuru 3y agodepends on the place of work. mine is also useless. the manager is clueless so some team members just tells every single thing they did for 15 minutes for clout with the manager.
- HellDunkel 3y agoJust my experience. A work culture where people approach each other without somebody telling them to do so is much better. Respect of each others time is also crucial. Get the motivating factors right and you dont need to bore the x out of everyone.
- arkey 3y agoIndeed, and I would even say that this applies to any meeting you can think of. However if you get the purpose of the meeting straight and somehow manage for everyone to properly collaborate, you'll get a 3-5min daily meeting that easily enables efficient collaboration and awareness.
- dboreham 3y agoDiscussions that should be 1:1 become 1:N, wasting the time of (N-1) people.
- mcv 3y agoDiscussions, yes, but discussions aren't for the standup meeting. Those are for informally updating everybody on what you're working on and whether you're stuck on anything. They lead to 1 on 1 meetings to solve those issues.
- bshacklett 3y agoThat’s the problem. Most teams don’t have stand-ups. They have gigantic status meetings on a daily basis, which is rarely valuable. Give me a meeting every day to get people to talk about blockers, but it should be 15-30 seconds per person at most, and it should be scheduled outside of productive hours (easier said than done).
- vitaflo 3y agoAnyone who cares what you’re working on can look at Jira. And if you’re stuck you shouldn’t be waiting for a meeting to tell people this. Standup are a total waste of time.
- wizofaus 3y agoMany are. But I've been in more than a few that resulted in discussion that ultimately saved many many hours of time that would otherwise have been spent on something that wasn't necessary. Actually the only thing I dislike about stand-up is struggling to remember everything I did the previous day, then realising I've forgotten to mention one or two key things after the meeting's ended, and wondering what everyone thought about the fact I apparently did so little... (which is silly, I know, but we're all human).
- mcv 3y agoJira never tells the entire story. And of course you can also reach out to people outside of the standup meeting, but that doesn't make them a waste of time. They can be quite effective, and they really do not take much time.
- dragonwriter 3y ago> Discussions, yes, but discussions aren't for the standup meeting. What actually happens in a standup meeting tends to be a mix of: (1) What theoretically belongs in a standup meeting, which is a meeting that should have been a kanban board plus identification of blockers that have been deferred for the standup rather than properly addressed when encountered and, (2) tangents into discussions which should be 1:1 (this especially happens when blockers are discussed, because people want to help get them unstuck.)
- arkey 3y agoAs others have pointed out, that's not what a standup should be for. Any tool, process or structure that is not being used properly tends to be annoying and useless. The problem is therefore not with the concept of a standup, but rather with how they are usually run. Running efficient standups, or any sort of meeting at that, is a skill.
- TheGRS 3y agoI don’t find mine useless, but I focus a lot on prioritizing and un-blocking people. The tasks we have are usually very different between engineers though so I can see why someone would find that useless time.
- gardenhedge 3y agoMine are also useless. Communicating with your team is super important but the mandatory status checkin when team members are working on unrelated things is pointless and draining.
- wizofaus 3y agoThat's a definition of "team" I've never heard before - "people working on unrelated things".
- starttoaster 3y agoPretty common in “DevOps” teams, in my experience. Some people are working on some autoscaling CI runner server initiative, some are working on writing code, some are fixing issues in CI pipelines, some are hardening the security of kubernetes clusters, etc. Their goals are completely unrelated to the others but is all work that falls under their team’s umbrella, and needs doing. Equally common in operations roles for the same reasons. Lots of servers and networking gear. You might be changing failed hard drives in a RAID array while someone else is patching servers while somebody else is upgrading some 20 year old Cisco firewall. None of these three people rely on the work the other is doing. Especially if they’re working in different server cabinets.
- wizofaus 3y agoWhy even call it a team then, and what would be the point of stand-ups for such a group?
- starttoaster 3y agoBecause it is a team. And, exactly, now tell that to our managers.
- gardenhedge 3y agoExactly. I work in a team that has multiple products so different team member can be working on different products, different priorities, different deadlines and for different stakeholders.