4 ms·
On the other hand, its very common for a team member to get blocked and not know how to get unblocked. A (occasional) standup can get them past that. And one bl
by JoeAltmaier 10y ago
On the other hand, its very common for a team member to get blocked and not know how to get unblocked. A (occasional) standup can get them past that. And one blocked team member can quickly become the long pole on the tent.
Standups and agile are quite useful, especially for new teams or teams of greener developers. Which, in our growth industry, is 'most teams everywhere'.
If you're part of a team that's worked well for months or years, then the utility is greatly diminished. I think standups can gracefully fade away after some months.
- Meai 10y 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 10y 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 10y 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.
- kisstheblade 10y agoIf someone gets blocked that someone better ask for help instead of just doing nothing. How does some daily ritual help with this?
- lj3 10y ago> its very common for a team member to get blocked and not know how to get unblocked. Is it? I haven't seen this very often and only with very junior engineers. Anybody with even a modicum of experience knows to ask for help when they're stuck. On the other hand, what I have seen all too often is an experienced dev blocking everybody else because of poor scheduling by the manager. Oftentimes, there's no way others can help with this. The dev knows what needs to happen, but it takes time and the dev just needs to do it. This makes every standup a humiliation. 'Is Joe still blocking Ted and Tara? Can you speed it up, Joe?'
- Meai 10y agoThat is exactly how I see and have experienced it as well. It's part of why I called it a motivation killer but I didn't go into more detail. Not only because of the accusatory thing but also I actually like to surprise my colleagues with cool features and issues I solve, surprising them with my speed even. If I attend a standup, I need to report that I'm working on these things so the surprise is gone. All my motivation to get them done asap is gone. Likewise, I can't do my own "secret" time planning anymore. I like to finish some mandatory feature fast so I can squeeze in a little extra cool thing I wanted to do for a long time. If I have to explain and justify this stuff, the manager will step in and urge me to do other mandatory things instead. It's such a mindkiller.
- bhauer 10y agoWhen I manage teams, I love having productive and self-motivated people like yourself on the team. As long as you are able to complete the scheduled and required tasks, if by being light-touch with process, you are motivated to contribute above and beyond, the whole team reaps dividends. I have seen such members contribute great tooling upgrades, features to reduce administrative overhead, automation mechanisms, and even delightful user-facing features. In my opinion, processes are designed to resolve or prevent dysfunction. An extra-productive team member that completes assigned tasks and adds in some of their own creativity on top is generally not a source of dysfunction, so I prefer to encumber such people with as little process as feasible. I for one love engaged productive developers who deliver bonus features of the sort I mentioned above and I find over-processing curtails those bonuses.
- gbersac 10y ago> its very common for a team member to get blocked and not know how to get unblocked. In this case just post the question of your team channel on slack.
- Too 10y agoBlocked beginners usually know how to ask their way out of blockers without standups. Another bigger problem with beginners though is the "creative" beginner. For those a stand up is a good place to catch "I just started writing a parser for X to solve problem Y" when there already is a company standard X-parser that the beginner doesn't know about.