4 ms·
> On the other hand, its very common for a team member to get blocked and not know how to get unblocked Yes of course that can happen and I said so, which mean
by Meai 9y ago
> On the other hand, its very common for a team member to get blocked and not know how to get unblocked
Yes of course that can happen and I said so, which means that he should ask whoever is blocking him how to proceed. If he doesn't know who it is, he asks the manager and he will direct him to the right person. If there is literally no way to proceed, he will work on another issue in the meantime and inform the manager that he's blocked on the more important stuff. If there is some way to speed it along together with multiple other people, it will come up when he talks to that first guy. Obviously waiting for the next standup tomorrow is a ridiculous proposition, so standups solve a problem for 1 time of the day requiring by definition more people than should be required because everyone is in it instead of pulling the people in that need to be pulled in for that specific block or feature.
I don't even know how people defend standups, they usually say something like "hey yeah, I know it's mostly useless but it's just for 10min a day". Absolutely unacceptable. Now I get to the last line of your post, and it's such a relief: "I think standups can gracefully fade away after some months."
Well you should tell the other proponents of standups because I can guarantee you that this never happens.
Standups might be a good idea in the starting phase of a projects but frankly even then it's debatable and then you would just call them meetings.
- JoeAltmaier 9y agoGreen developers can not know who to ask (they're new, right?) or not know when or how to ask. They can be quite tentative. We're talking Engineers, not Sales guys. Some folks don't think they need standups, ok. But in reality, many folks benefit from them.
- kpil 9y agoI agree, even experienced developers can get stuck barking up the wrong tree. There are at least one or two exchanges like this every week in my team: Dev A: - I'm working on X, and will just need to fix the code for Y to handle it. It's a bit messy but I'm probably done tomorrow. Dev B: - Eh... I think you need to do something to the Z code, we can take a look after the meeting. Dev A: - Sure.