3 ms·
I think that the people who don't like standups, are the people who have never been a part of one that works well. This isn't surprising, because most don't wo
by kube-system 7y ago
I think that the people who don't like standups, are the people who have never been a part of one that works well. This isn't surprising, because most don't work well.
There are two critical things that a leader must do to run an effective standup:
1. You must have a leader who is willing to enforce the rules in order to effectively extract the right information to support managerial tasks (and not arbitrarily, but through team buy-in), and
2. They must be willing and able to understand most of the technical intricacies of the tasks taking place.
In my experience, most organizations' standups are run by people who fail at one or both of these.
Maybe they'll put in a PM who enforces the rules, but doesn't understand (or doesn't care to understand) the tasks the developers are doing with enough detail to be an effective facilitator. They act as a note-taker, letting the developers manage themselves ad-hoc, and don't ask questions unless someone specifically brings up a blocker. This can work with a team 100% full of self-starters who are comfortable with asking hard questions of each other, but that's your only hope.
Or on the opposite side of the spectrum, you have organizations that put more senior developers in that role. Then, you often end up going down design rabbit holes until you've run out of time, and you never end up doing the tasks that you actually needed to do: planning everyone's time effectively, and recording/communicating progress so that stakeholders expectations are correctly managed.
In both of those failure cases, you end up failing to deliver a quality product on time and/or fail to communicate expectations to stakeholders. In the first case, you made a plan, but it wasn't a full picture. In the second failure case, you had all of the right tasks figured out, but you failed to plan and communicate it.
- WJW 7y agoIf most people are unable to do it right, the act is too difficult. Saying "it works fine if everyone does as they should" just ignores that people don't usually do as they "should" and is not very useful.
- kube-system 7y agoI disagree. Most new ideas implemented in the workplace come with generational learning curves, even when history has shown them to be good ideas. This is just a cyclical skills gap. Few people running software projects have formal study that spans both management and software. Many have neither, in my experience. Sure, formal study is not a requirement for good performance, it sure helps to get everyone in an organization on the same page.
- loopz 7y agoIf the leader doesn't even know why they're "standing up", how will anyone benefit from it? Blindly following rules is just sorry-ass incompetent BS. Period. In my experience, the few periods stand-up works (comedy aside), is when the leader (and noone is gonna do it without one!) understands what is to be gained by the people involved. Unfortunately, whenever something randomly works, the next random reorg negates that overnight.
- scruple 7y agoI've been in stand-ups that worked well (rather, teams that had the degree of cohesion necessary for a stand-up to work well). But, even when you do have a good, productive, useful, fluid stand-up with some team it won't last forever. Roles change, people change, teams change, projects change. There are too many things that have to align to make these things provide their stated utility over the long-term. YMMV.