My rule of thumb for assessing a team is based on two simple questions: 1. Do people in the team work towards the same goal? 2. Do people in the team depend on each other? If the response to both questions is positive then by all means, have standups. In other cases, have a good look at whether it makes sense to call them a team in the first place.
They're unrelated tasks because there are no dependencies between them, and there is absolutely no reason why I should have to sit through bob talking about his day.
EDIT: Spelling.
Take ownership of the standup, don't just passively sit there and then complain afterwards what a waste of time it is.
And to clarify, I also find daily standups to be tedious and generally unhelpful. Once or twice a week seems to be the sweet spot (for me/my team).
There are of course many ways to run a productive team.
I find the team needs to be at most 6 people, otherwise you probably need to split the team for daily standups to work.
1. Everyone explicitly has the responsibility to say "this is going too deep, let's continue it outside of standup" when needed.
2. Having a timer visible that resets after each person's update. This makes it clear when one person's update is taking too long. We were able to get rid of the timer once we had the flow down.
Also, it's crucial that everyone on the team feels comfortable saying: "these standups aren't a good use of our time, let's make a change". That's how those techniques were introduced.
I've also worked at places where a 20 person standup took < 10 minutes and helpful b/c sometimes someone not on your team will know how to fix your blocker and just help you out afterwards.
I think as long as you have a standup czar or just post your updates to slack, then it's a super useful meeting. If it ever goes over 10 minutes then whoever is running it is just making everyone late for work.
Why does it depend on the size of your team? Teams involved in agile development (where they do the whole daily standup kerfuffle) are supposed to not get to 10+ people. That's like the third thing on the agile coach's slide.
Besides, why does it take a full-team standup to find out someone has expertise and ideas in an area that you didn't know about? Are the lead developers/managers sleeping at their desks? Guiding and bringing people together is one of the things they're paid for. They should know who's good at what, and steer the right people (or the right tasks) towards them. If they aren't doing their job, what the team needs is people who do, not one more thing that developers have to figure out on their own time.
As for brainstorming -- it shouldn't be unexpected in the first place. Not on a regular basis, anyway. If a developer needs that brainstorming session, they should have the means to make it happen, with only the interested people attending. If they need it, but don't know they need it -- especially common, and especially excusable for junior developers -- that's why we have lead developers and managers.
And meetings are not the only way to spread information! If a team has 10, 15 members or more and it's spreading information by word of mouth alone, whether 1:1 or in meetings, that's already a problem. At that point you should have things documented. New members should have an M that they can RTF and ask experienced team members about. If a team got to that size and the only way to spread information is in person, that's something they should remedy, not keep doing!
For a concrete example: if I track a performance problem down to a small part of an open-source piece of software, it isn't realistic for managers/lead developers to know if anyone on the team has experience with that piece of the software. But if I mention that in standup, it will immediately be clear if anyone has expertise that is valuable.
I've never seen a high performing team that didn't regularly have ad-hoc brainstorming sessions (i.e. you say what you are planning to do and someone says "have you considered this"). Like I said, there are many runs to run a productive team, but standup can be a good place to start that discussion.
Keeping track of people's skills and expertise is part of their job description. If they don't, how are they going to help them develop and steer their careers? Not knowing every single thing they've worked on is one thing, but knowing (as in your example) who is likely to have used that piece of software, or who has experience troubleshooting performance problems involving that piece of software's functionality, is definitely their responsibility.
> For a concrete example: if I track a performance problem down to a small part of an open-source piece of software, it isn't realistic for managers/lead developers to know if anyone on the team has experience with that piece of the software.
Certainly -- but that doesn't justify having a stand-up meeting every day. It's not realistic for managers/lead devs to know if anyone on the team experience with a particular piece of software, but it is realistic for them -- or for any developer, for that matter -- to be able to find that out without dragging everyone from their desks for half an hour or more.
In my experience, standup has almost no cost and is generally enjoyable - people typically like talking about what they are doing and getting thoughts/advice. But if your standups are "half an hour or more", they clearly don't have much in common with the standups I've done. I would propose that maybe the problem is your standups are poorly run, not that the concept itself is bad.
As for timing: if you have a 10- or 15-people team, allowing for even just two minutes per person -- which is barely enough to cover a non-trivial problem -- easily gets you to 20-30 minutes. It gets shorter if all updates are in the form of "no news is good news", but then the meeting could have just as easily been an email. It also gets shorter if the problems really are so trivial that fifteen people can describe all of them, and their solutions, in a couple of sentences, so that no one talks for more than 30 seconds -- but then are these problems really so big that you need to hold a meeting that everyone attends, every single day?
I don't think the concept itself is bad -- just that the arguments for efficiency aren't convincing when it comes to large teams. I doubt that you can really disseminate useful information in this format, and even if you could, there are way more efficient ways to do that.
Edit: If these meetings are held just to make sure all updates are given regularly, often, and in the open, with all the consequences this has (good ones, like everyone being on the same page, and bad ones, like opportunistic managers taking the chance to use this as a way to pressure their team), that's great, but let's be frank and admit it.
A real scottish standup is a few minutes -- 5 or 10 minutes. 15 max if there are lots of people and lots of things to cover.
How much useful stuff do you think a developer can fit in 20 seconds of speech -- which is about all they get if you want to fit a 15-people meeting in a ten-minute timeslot?
Once a team grows past a certain size, either you keep the discourse substantial -- and end up with 30-minute meetings -- or you cut everyone short, and end up with ten minutes of smiling and saying the right buzzwords.
1. What did you do yesterday?
2. What are you doing today?
3. Any blockers?
My company is blessedly stable, but for instance at my wife's employer, there are teams that have had 300% turnover in the two years she has been there.
I think this kind of endless short-term firefighting is part and parcel with the micromanagement that daily standups embody. When nobody actually has any experience, or built any trust over time, the whip lays on heavier to keep people in line and pulling in the same direction.
It really shouldn't be much cognitive load to listen to what other people are working on for 10 minutes. If it is, it might mean the standup is running at the wrong level of abstraction or perhaps you aren't really a team that has a shared goal.
> If it is, it might mean the standup is running at the wrong level of abstraction or perhaps you aren't really a team that has a shared goal.
Or maybe the problems other people are working on will take more than 10 minutes for any reasonable input.
[1] https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum... - page 7
I will say, Scrum was really helpful for us, but only because we took "iterate on your process" seriously, and had a culture where teams could experiment with their process.
In the end we outgrew it, but Scrum helped us reach the point where we could do so.
Small teams are better, but not always possible. Agile is about having team mechanics that make your specific team more productive and changing them as your team changes.
The nature of the work probably also helped because tasks took a long time so on any given day only a handful of the people would have substantive updates.
I think this is the key difference between teams that like stand-ups and teams that don't. In the teams I've worked in, our work was highly relevant to one another, so knowing daily where everyone was with their tasks is usually interesting to everyone.