News for hackers. Stuff that matters.
Re:Daily standups should be async by hyperpape on Friday May 15, 2020 @01:51PM (#23195101)
I think if your standup can be async, then it's ineffective, and you should get rid of it. And to be clear, that's fine! Not every team needs standups.

The only value in a standup is when team members actually share ideas about what they're working on. The detailed conversation happens outside the standup, but the purpose of the standup is just to get that moment of "I know about that, let's talk".

In that case, having everyone in a room (real or virtual) at the same time is more efficient than asynchronous updates. With asynchronous updates, people are in meetings, in the bathroom, not online yet, etc, and you have higher coordination costs.

I've been on teams that have effective standups, and teams that have worthless ones. I know what each one looks like. But for the life of me, what I can't figure out is why some teams have good ones, and some don't.

Re:Daily standups should be async by jayd16 on Friday May 15, 2020 @03:18PM (#23196226)
I disagree. Obviously if they're async we should please stop calling them "standups" but they can still fulfill some of the goals of a standup.

You want a way to voice your status, hear other's statuses, hear blockers, and reduce duplicated effort. You can do all this with short, daily, async updates. The synchronous fashion of the standup is mostly a factor of verbal communication, not a feature.

Standups are usually partially async as items that arise should be dealt with outside of the meeting.

It still needs to be daily and time gated such that the team can consistently read everyone's status.

Forcing the team to pay attention is probably harder in an async conversation chain than a meeting but I don't think ineffective is correct.

Re:Daily standups should be async by mrkurt on Friday May 15, 2020 @03:23PM (#23196286)
> Forcing the team to pay attention is probably harder in an async conversation chain than a meeting but I don't think ineffective is correct.

I think this is a feature. If people aren't paying attention to asynchronous information, there's a problem. Either the information isn't useful or the team isn't functional.

Re:Daily standups should be async by jayd16 on Friday May 15, 2020 @03:29PM (#23196357)
It might fall under "non-functional team" but active listening/reading of usually banal but sometimes critical information is simply not an easy thing to do in a routine format. The information in a standup is team-wide because you do not know what will be important to who. It takes some amount of skill and discipline from the team.
Re:Daily standups should be async by karatestomp on Friday May 15, 2020 @05:18PM (#23197550)
Part of this is because the standard format encourages including shit that no-one cares about, or that a glance at the issue tracker or repo activity would (should...) clarify immediately if anyone wants to know. If your "no blockers" updates could be written by a very simple script maybe don't bother with those parts.

Or, god, worse if it's manager-centric and everyone's listing every little damn thing they did yesterday just to make sure they sound sufficiently busy. Ugh. No one gives a shit (except your manager, if they're bad and letting standups be used this way) do you need anything? No? Then move on.

Re:Daily standups should be async by mrkurt on Friday May 15, 2020 @03:34PM (#23196407)
We 1000% agree on this, but it's still fun to talk about.

I think that's just low signal to noise. It definitely takes skill and discipline, but it's also a matter of improving habits. Standups were originally a "better habit". There's a cost, though, especially as teams are more distributed (and diverse).

Re:Daily standups should be async by jayd16 on Friday May 15, 2020 @03:42PM (#23196500)
Agreed. It seems like most of these problems arise from cargo culting the habits without understanding the purpose behind those habits.
Re:Daily standups should be async by protonimitate on Friday May 15, 2020 @02:21PM (#23195511)
Agreed. Async stand ups are an agile smell.

If you can successfully get unblocked async over slack/email/whatever, there isn't a need a for standups. That just means you have a functioning line of communication for your team.

Stand ups should solve the problem of "I need to get unblocked and I can't get my teams attention effectively". If async "standups" solve that, great. But it's not a one size fits all solution, and imo, shouldn't even be called a standup.

>But for the life of me, what I can't figure out is why some teams have good ones, and some don't.

IME it's the level of interaction of product/management/scrum-masters that make the difference. Good standups consist of just engineer focused updates/requests. Bad ones are progress reports and have participation of anyone not actively contributing to the sprint.

Re:Daily standups should be async by mrkurt on Friday May 15, 2020 @02:25PM (#23195557)
Agile is smelly. People getting blocked in a team small enough for a standup is a concerning smell. Bad standups are a smell, and also seem to be the norm.
Re:Daily standups should be async by waheoo on Friday May 15, 2020 @03:50PM (#23196621)
I suspect all these smelly meetings might be an agile smell itself.

Maybe agile doesnt quite actually support our needs. Maybe some frequent socialising is a need. Maybe sucking every last second out of our day in the name of productivity while having zero benefit on the true goal is just one huge smell.

Re:Daily standups should be async by Benjammer on Friday May 15, 2020 @03:00PM (#23195990)
Literally had a manager say "oh, they're supposed to be for unblocking? I just thought it was an easy way for me to report up the chain on what my team is working on, that's why I told people to just write it on Slack to make it easier for them." ugh
Re:Daily standups should be async by xref on Friday May 15, 2020 @10:04PM (#23199819)
Stand-ups becoming a status report to justify your employment is a common end state of “going agile”. Meeting gets longer, people add more trivial minutiae, nobody wants to look the laggard
Re:Daily standups should be async by hashmal on Friday May 15, 2020 @03:45PM (#23196538)
> Async stand ups are an agile smell.

That thinking is an agile smell. Teams choose their own processes.

Re:Daily standups should be async by platz on Friday May 15, 2020 @04:31PM (#23197053)
No reason to discuss anything then I guess, everyone needs to just invent their own rules without talking to anyone else.
Re:Daily standups should be async by hyperpape on Friday May 15, 2020 @02:26PM (#23195570)
I have had low value standups with groups of just three developers or six developers, so I don't think that's enough. I agree that the feeling of "I have to justify my work to an external party" is a negative.
Re:Daily standups should be async by temac on Friday May 15, 2020 @04:24PM (#23196995)
> Stand ups should solve the problem of "I need to get unblocked and I can't get my teams attention effectively".

That's an interesting claim, but has it be proven or even seriously studied? I have an extremely hard time with open meetings talking without any depth about various subjects which I don't care about 90% of them; it might make me space out and at risk of missing the parts that I could actually be interested in or contribute. Plus this cultivate the importance of oral transmission, with informations easily lost and inaccessible for people unable to participate for various reasons. Maybe a good structured IM (e.g. dedicating a chatroom exclusively for that) could make it work better? I think it is important that the medium be the same for synchronous and asynchronous people.

Daily meetings can be extremely useful in context of routine transmission of info, mostly on always the same well-defined topics + a small amount of random very important things. The important infos must be hierarchized, you can not just drop them in the middle of a stream of boring "I continued to develop X yesterday and will continue to do it tomorrow". So on open engineering subjects, some people may like it and that may be effective for them, but I really want to know if this is the majority of people / for the majority of projects / ...

Re:Daily standups should be async by jayd16 on Friday May 15, 2020 @03:24PM (#23196295)
The unblocking in a standup is almost always async. They're there to have a defined place for public knowledge transfer. You usually shouldn't drag down the standup with a prolonged conversation. You can take care of it after in an async way even with in person standups.

Focus on surfacing problems not solving them.

Re:Daily standups should be async by im3w1l-alt on Saturday May 16, 2020 @09:28AM (#23203204)
Standups always bored the shit out of me because a huge fraction of time is spent listening to irrelevant stuff. I wonder if speed dating might be more stimulating.
Re:Daily standups should be async by PragmaticPulp on Friday May 15, 2020 @02:38PM (#23195704)
> I think if your standup can be async, then it's ineffective, and you should get rid of it.

I agree, with one caveat:

If you tell engineers that standups can go async or be cancelled if they're ineffective, they will find creative ways to make the standups ineffective.

Poorly run standups are bad. Standups where the engineers are half-engaged are bad. But having a well-run standup that synchronizes the team, spreads vital information, and keeps people accountable is truly valuable.

However, a good standup requires everyone to put in effort to keep it useful, fast, and on track. If everyone decides that standups are a waste of time, it becomes a self-fulfilling prophecy as the leads have to pull unprepared reports out of each individual, summarize things because people aren't listening to each other, start over because people are arriving late, and so on. If you tell people the standup can go away if it's bad, you've accidentally incentivized those people to make it bad enough to get it cancelled.

Re:Daily standups should be async by karatestomp on Friday May 15, 2020 @03:11PM (#23196143)
> If you tell engineers that standups can go async or be cancelled if they're ineffective, they will find creative ways to make the standups ineffective.

What the hell? Have you actually seen this happen? I can't imagine someone jettisoning something that makes their work-life easier and is an extremely low time commitment, just because you tell them they can. I can imagine them changing it to something else if that's more useful and cheaper, time-wise, or getting rid of it if it's of very low utility. Lots and lots of standups are the latter, from the IC's perspective. A lot of "talk to the manager who's the actual audience for the meeting, everyone else dozes off" standups. "Ten people and only two others are actually on my project, and we talk all the time anyway". That kind of thing. Plenty of that out there. I could see them wanting to get rid of those. I mean if people are putting so little effort into the standup that it makes them bad, and the standup is for them, supposedly, then maybe that's a sign it isn't valuable to them?

> If you tell people the standup can go away if it's bad, you've accidentally incentivized those people to make it bad enough to get it cancelled.

Again, this makes no sense unless from their perspective it already is bad and they just need to convince you it is, too.

Re:Daily standups should be async by overgard on Friday May 15, 2020 @05:14PM (#23197496)
As an IC, I've honestly just not attended many (any?) standups that provided value to me. I understand if it's for someone elses benefit, but that someone else is most assuredly not me.
Re:Daily standups should be async by PragmaticPulp on Friday May 15, 2020 @04:19PM (#23196938)
> What the hell? Have you actually seen this happen?

Yes, this is from personal experience.

> I can't imagine someone jettisoning something that makes their work-life easier and is an extremely low time commitment, just because you tell them they can.

Look at it from a different angle: If you tell people you're thinking about replacing standups with something more efficient, you've tipped your hand that the current situation might be inefficient. Suddenly, people lose interest in participating in the status quo because even management doesn't believe it works, so the quality of preparation and engagement goes down. This creates a self-fulfilling prophecy where the standups become more and more useless over time.

On a similar topic: I worked in a department that tried to adopt a version of Elon Musk's famous "If you're not adding value, walk out of a meeting" rule. The people who hated meetings made it a point to not add any value in meetings, so they could get up and leave as soon as possible. This forced everyone else to have followup 1:1s with the people who walked out so they could be essentially re-capture their required meeting participation.

> Again, this makes no sense unless from their perspective it already is bad and they just need to convince you it is, too.

Two different topics. People can still dislike standups even if they're helpful.

A lot employees are drawn to work concepts that reduce their workload at the expense of their manager's. It's less efficient to make a manager play a game of telephone to spread information around than it is to get everyone together for a 15-minute standup, but if someone thinks they can reclaim those 15 minutes and force their manager to bring them any relevant info, it's a net win. In the real world, this becomes an inefficient and lossy system, but it sounds good if all you see is an extra 15 minutes saved in your day.

Re:Daily standups should be async by gowld on Friday May 15, 2020 @10:07PM (#23199841)
That's hugely backwards, sacrificing 10 people's time to help 1 is what's inefficient.
Re:Daily standups should be async by karatestomp on Friday May 15, 2020 @05:05PM (#23197392)
> If you tell people you're thinking about replacing standups with something more efficient, you've tipped your hand that the current situation might be inefficient.

Oh, well yeah, if you put it like that you might have a problem. "These processes are for you, if they're not serving the team or if you think something else could work better, let's talk about it and fix it" as a blanket policy for agile policies (which is supposed to be the norm in agile) is another thing entirely.

> On a similar topic: I worked in a department that tried to adopt a version of Elon Musk's famous "If you're not adding value, walk out of a meeting" rule. The people who hated meetings made it a point to not add any value in meetings, so they could get up and leave as soon as possible. This forced everyone else to have followup 1:1s with the people who walked out so they could be essentially re-capture their required meeting participation.

I have a feeling better meeting planning & pre-meeting communication would fix that and let you retain the "walk out if you can" rule, if desired, but it'd probably have to be so good that it'd far exceed the norm for that sort of thing, so yeah, probably impractical most places.

> A lot employees are drawn to work concepts that reduce their workload at the expense of their manager's. It's less efficient to make a manager play a game of telephone to spread information around than it is to get everyone together for a 15-minute standup, but if someone thinks they can reclaim those 15 minutes and force their manager to bring them any relevant info, it's a net win. In the real world, this becomes an inefficient and lossy system, but it sounds good if all you see is an extra 15 minutes saved in your day.

Yeah, that's probably true in some cases. I still think if you're having 15 minute standups and cutting that doesn't reduce total time for the process, that's strange. Though, yes, it might cause your manager to spend a little more time on it, personally—but taking two or three minutes to scan standup messages and make sure followups happened where relevant (most days this ought to be basically no work) seems like team lead stuff anyway, not manager stuff, which can just mean "whichever developer you've told to do that" if you don't have a designated lead (~every developer I've met over age 25 is very eager to do anything that can be described as leadership on a résumé so finding someone to take that on ought to be easy) and I'm not sure why a manager'd need to be involved most of the time chatting with anyone but the lead over standup stuff, and then only if their input's needed to unblock something or bring in someone outside the team who's too far above the lead's "pay grade" for them to do it themselves, which'd usually be a "let's talk after the standup" conversation anyway (though maybe not, I guess, if they're taking more than five minutes flat).

Re:Daily standups should be async by nogabebop23 on Friday May 15, 2020 @02:47PM (#23195815)
>> having a well-run standup that synchronizes the team

and this is (I believe) the point of stand-ups. Doing this "async" seems at best weird/hard and at worst impossible.

The original post is for a prduct selling async status reporting, which is realy not what stand-ups should be about.

If you want to have a daily status report, by all means do it remotely or async or whatever works best. If you want to synchronize the team, well the most obvious and effective way is to actually bring them together in the same temporal space (remote or otherwise). You don't need to do this for problem unblocking or status updates, but don't tell me you're doing a distributed async status update as a method of team synchronization.

Re:Daily standups should be async by PragmaticPulp on Friday May 15, 2020 @04:21PM (#23196955)
> The original post is for a prduct selling async status reporting, which is realy not what stand-ups should be about.

Exactly. Once you've reduced standups to async individual reports, you lose the team communication benefits.

In my experience: Once you lose the team communication benefits, people give it even less thought and energy, so the value continues to decline until the concept is abandoned altogether.

Re:Daily standups should be async by jakub_g on Friday May 15, 2020 @04:58PM (#23197310)
The daily status update has different role for different people (devs, scrum master, tech lead). It might be useless for devs but valuable for scrum master, for example.

The dynamics also depend on # of people involved - the fewer, the more effective.

What we did in my last 2 teams to make standups better:

Team 1: move it from 10 AM to 11h45 (just before the lunch). Advantages: 1) Not stressing out people who are late; 2) Not breaking the work of people who arrive early; 3) Keeping it short - since it's before lunch, it can't last forever because people want to eat.

Team 2: move to slack e-standup. Advantages: 1) and 2) above; 3) Async, so you can do it early, late, or even the evening before; 4) It takes 2 min for each person, not 20 min and you don't have to stare in the floor while your mind is somewhere else; 5) Avoiding "ummmmm whaaat did I do yesterday ummmm let me think" x 10.

Re:Daily standups should be async by pathseeker on Friday May 15, 2020 @04:31PM (#23197055)
>The detailed conversation happens outside the standup, but the purpose of the standup is just to get that moment of "I know about that, let's talk".

If the purpose of the standup is to tell people what you're working on and not have any detailed conversations, then that's the best argument for making it async that I've heard.

The optimal standup seems to be everyone posts to channel by 10am what they are planning on doing for the day and if they want help. Everyone reads each other's and replies as needed. Done

Re:Daily standups should be async by ljm on Saturday May 16, 2020 @02:49PM (#23206072)
I agree with some of what you say, but not all of it.

Back when I first switched to a scrum master role, way back in 2013, I was pretty full on with prescribing the purpose of certain ceremonies. The standup was for X, and the sprint planning was for Y, etc. We had built a successful business model around that back then so it wasn't necessarily being dogmatic about agile and scrum, but knowing our recipe for success and sticking to it, so we ran a tight ship that also allowed us to put our feet up and work more sustainably.

I find myself in a similar leadership role now and, perhaps moreso due to us all working from home since the end of February, I've taken a completely different tack. I really appreciate what agile and scrum embody but after several years of doing it and getting comfortable with my own role in that dynamic, I've pretty much tossed the 'rules' out of the window and gone straight back to basics with the original manifesto.

My team now does 'asynchronous standups' but we don't call them standups. If my team wants to jump on a call to chat, I'll be there, but otherwise, a quick check in when they come online and start their workday is more than enough. That could be at 7.30am or 12pm for all I care. It still performs the function of a standup, and it fits the purpose we've given it.

I'm not really interested in selling proper scrum to my team the way I used to, now I'm far more keen to let them self-organise and let their work, their happiness, and their behaviour speak for itself. They always have the option to introduce more process if they want to.

Re:Daily standups should be async by the_gipsy on Friday May 15, 2020 @05:28PM (#23197667)
Why would you wait until a specific time of day, if it's so important (blocker)? Why waste everyone's time, every time?

Either it's a glorified status update, or it's incredibly inefficient compared to just resolving issues on the spot or at appropriate times.

Re:Daily standups should be async by MuffinFlavored on Friday May 15, 2020 @05:05PM (#23197387)
> The only value in a standup is when team members actually share ideas about what they're working on

Or for management to track what you are doing and hold you accountable to deadlines and ask why you are late.

Re:Daily standups should be async by mstade on Friday May 15, 2020 @05:09PM (#23197432)
Daily standups for status updates and whatever is – in my experience, 15 years at this point – entirely useless. As a way to shoot the breeze in the morning just to say hi though, it's really effective, especially when remote. I've been working 100% remotely for the past five years, give or take, and if I didn't have those 15 minutes of just shooting the breeze with people I'd never get my water cooler fix. Your mileage may vary, I guess.
Re:Daily standups should be async by hidiegomariani on Friday May 15, 2020 @03:41PM (#23196487)
it depends. mostly on team size and workstreams. when the team is working at different unrelated things the standup is near to useless and it's used only to micromanage people. if you are a close-knit team working on the same workstream/feature then yes is beneficial even then in my experience daily standups are overkill. most of the time bi-weekly is more than enough
Re:Daily standups should be async by mrkurt on Friday May 15, 2020 @02:23PM (#23195525)
I think you're redefining what a useful standup is, a little bit. I agree with you though, I'd just phrase it as "standups are pretty useless" and "it's good to have people share context what they're doing".

So maybe that's part of the problem, standup means whatever it happens to mean. You could replace the entire title of this post with "context should be shared async".