It was a meeting for ourselves, not for management. There were no status reports to management, no gantt charts, no percentage estimates of completion, etc. Just: here's what I'm doing/not doing.
Fast forward a decade or two and I've seen good and bad use of this meeting form. But I still think it's a good idea, it just requires discipline to stop people from hogging air space or veering off into tangents.
That's my understanding of what a standup is supposed to be, and it's what my experience of them has been. THIS is useful. It's in particular useful if you have devs on the team who tend to get kinda "wound around the axle" on problems rather than speak up or seek help.
There will always be devs who think any meeting is by definition a waste of time, and you can't make those people happy, but a true brief standup meeting as described here is SUPER useful.
(Daily's probably too much though.)
Personally, when I lead a team, I keep abreast of what people are working on and ask them if they need help, or tell one of the more suited senior guys to offer a hand if it's an area I can't easily help in.
I imagine the standup helps more when you're lead is a non-technical scrum master guy who doesn't have much of a personal relationship with the team.
On the latter point I typically buy my team members fancy coffees and the occasional lunch, and it's easy to get on with them if you care about their careers, so I've never needed a standup.
Either way, I'm not so sure the statement means much. The point of agile is to do what's helps, so if a standup is useful for the above reasons, it's entirly possible that another approach solves the same problem, negating the need for the standup.
But the key thing is that the daily standup is NOT a status report for management! That should not be its purpose! It is for the team members to sync with each other, not a daily report for task management.
The manager has plenty of other ways to gather status updates and feedback as you note.
Your tone is slightly rude considering you're essentially agreeing with me.
You'll need to note the entire thread for the context of my discussion. I was specifically saying a good tech lead and other senior engineers can help engineers get unstuck without actually necessitating a standup.
For me, standups are fine if the team actually want to do them and find them useful, but 9 times out of 10 they're enforced by someone non-technical and require the entire team listen to people drone on justifying what they did yesterday.
Personally, I find the assumption that I can't communicate with fellow engineers without such a thing pretty insulting, but do understand that some of us do struggle with this thing, so it's different strokes for different folks.
But yes, in XP, the 'customer' or 'product owner' would not attend a daily standup. The purpose of the meeting was for developers to sync and maintain velocity and social and work cohesion.
Meeting with customer/PM was something that happened at the end or start of iteration.
Frankly, once things scale beyond that, where you have large teams of people disinterested in what's happening beyond their choice of specialization -- "agile" starts to not be a good match anymore.
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.
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 haven't ever felt this kind of pressure from management in my stand ups. We very rarely have anyone from management present anyway. The stand up exists for the benefit of the team, not management. It is not a status report for management.
I've been a bit of volunteer agile coaching in my area, and yeah, one example that always stuck with me was that the product managers and BAs just got renamed product owners, and they sat in every retro and attended every stand-up.
Funnily enough they were never available to the team during planning. They had important meetings on a Monday...
I tried to empathise to them that "stand-up and retro are solely for the team", but no dice. They still wanted that command and control.
If you need help or are block, you report that. Otherwise, no need for a "status update". It also helps that we do this in our eng-only channel, where no product/upper management are in, so only our team is privy to the information.
The one downside is that it can be a bit more difficult to get help on something highly important if everyone is tunnel-visioned. Luckily, we have a great engineering manager who helps orchestrate help in those situations or steps in personally if someone is blocked.
If that is the case, then why are you even in the same scrum team? What you have there is not a team by the sounds of it.
If you're still working on the same issue, then just say that. Keep the standup short. Of course this can also be a good time to notice a lack of progress; if you're spending days on an issue with little progress, are you stuck? Was the story badly defined? There could be very good reasons why it's taking longer, but again, the standup is a great time to notice these things and check if there's a way to help the issue along.
As others have said, when you're working on a team where there is significant interplay or varied, related experience, they're really useful. We work on an OS and have members of the team who happen to have experience using infra and tooling. There's no way you would necessarily know this without saying "Oh, I was struggling with this bit of stats collection infra" and somebody else says "Yeah, I worked on that on x project, y years ago. Let's chat after stand-up."
There are obviously other ways to seed this kind of thing, but brief stand-ups seem a good way of doing it.
The other thing that we tend to do is just say "Oh, I did x that doesn't really relate to the project yesterday, but that's not very interesting" and leave it at that.
Spot on. In many companies standup are used to put people on the spot and pressuring them to show progress and so on.
It's amazing how many people on HN don't realize that.
If you can't find something to say for a minute about a day's worth of work then you probably need to be rethinking how you're spending your days.
> if you need help you ask it anyway on the spot, there is no need to wait for the next standup for that.
I thought part of the reasoning for standups was to synchronize your interruptions, so instead of breaking people's flow throughout the day, you can line up all the cross-cutting concerns at the beginning of the day.
It sounds like you are not a team in the sense of a coherent body creating added value, but a line organization mandated agglomeration of talent under a specific manager.
When actually working together quick stand ups make sense, but for individual contributors they add very little added value.
However, the only way to know if the dailys are unnecessary or not, is not how they feel like, but what happens when you remove them.
All coordination work feels unproductive. But after a specific complexity is reached coordinated efforts of communication are the only way in which a large body of talent can function in a sensible way together.
While I would also like to do the daily status email, I see value in doing a synchronized standup. It helps planning for the day.
Not all people are great communicators and I’ve seen lots of developers spend days on tasks which should take 1 or 2 hours max. Standups highlight these issues, but you need to listen and go to these people in private to understand their problems. And you should absolutely take up people if they offer to help you.
I tend to bring pen and paper to remember what I wanted to say and to note when I here something that’s relevant to me.
He could not understand that "I had not trouble yesterday, and today I will keep going on my task" could be a useful update to the team. I mean, in general it isn't but when something unexpexcted happens you are supposed to say it, not something unique for every day. 90% of my dailies are basically: "I am still working on X, and its moving forward, continuing today".
Did the scrum master not feel able to intercede? Protect the process etc.
Why not join the meetup with afterwork drinks? That way you can really say what blocked you ánd talk about the things that you'd do in a standup...
That excludes certain segments of your workforce in ways that make HR sweat. Parents, alcoholics, people of faith... you've made attending the meetup more difficult.
Mandatory after work 'fun' can be highly controversial.
Not my experience, teams of that size I’ve been on do standup in 10-15 minutes.
I don't mean to imply this is a panacea. "Doing Agile right" is one thing, but business is about more than software development, and an engineering-led organization can of course ignore financial or marketing realities.
But there's an expertise-for-the-job phenom going here. Managing software development is a skill. It requires "navigating ambiguity," that favorite phrase of managers. It requires being able to expect and roll with punches, and chart a new course---every few minutes to every few months, depending on the context.
I suspect the best thing would be for boards to take a more active interest in their company's SD activities. Bring the CTO in, figure out the tech landscape the company is confronting. "Giving devs more power" is probably a no-sell, but "boards taking software seriously" might fly. And when you do that, you unavoidably become the devs who already have power.
I know, a digression, sorry. But it's just night-and-day, the diff between technical and non-technical management.
Are we talking adult employees here? :D Anyway, if I ever become employed, and will have to work on-site, I want the comfort token to be a stuffed baby gnu.
Exactly this... I couldn't care less what dev-no-3 is working on since its not impacting me and I could bet no one cared much what I said except the scrum-master.
A chance to briefly set out any blockers you anticipate for tomorrow/stuff you will need from other people.
But just as important; an end of day marker 'we're done - piss off home now - no working late'.
Early enough for the 6-3 worker might be well before the end of the day for a lot of others.
So true. At the last company I worked, the daily standups became absurd. We were forced to use a physical board which was always out of synch with GitHub and we were just repeating the same stuff that we already knew everything about.
Also, we had scrum retrospectives in which the new scrum master was throwing a yellow ball at someone when it was their turn to talk. WTF?! Does management think our brains stopped growing after the age of 5? You have a room filled with potentially brilliant engineers and you're treating them like toddlers. Do they seriously think that this is the right way to build a company which will make an impact on society?
What the hell is wrong with managers these days? Is there some kind of virus going around which is turning them into idiots or is there a global conspiracy to only promote idiots into positions of power?
When I was a manager, I always found it to be far more effective to have team members apply psychological pressure to their peers, rather than apply pressure from the top down.
Standups are best avoided by managers. I never felt the need for yet another meeting. In fact, an excessive number meetings are one of the main reasons I got out of the management business.
It sounds like a bigger a problem then standups; if everyone feels they are useless why is there no forum in which this meeting is being discussed and removed or recalibrated? It sounds like the team doesn't own their own process or doesn't talk to each other about process
Except for management, as standups are a simple way of keeping psychological pressure on developers and squeezing every last bit out of them.
I even saw once a developer on his last day throwing the speaker's token (a teddy bear) to the trash can LOL!
Everyone on the teams I worked on seemed to think that standups where useless, this showed clearly through the team body language and tone in those meetings.
Its an interruption on your work just when you just got started in the morning, now you have to stop and go to a meeting.
What people are working on is usually unrelated and of no interest to each other, and if you need help you ask it anyway on the spot, there is no need to wait for the next standup for that.
It's hard to come up with different things to say on the meetings, as there aren't many things that have changed since yesterday.