5 ms·
To echo another comment on here - Daily standups have been the most useful development I've seen in my 17 year career so far, I'm not sure why there's the hate
by Nursie 10y ago
To echo another comment on here -
Daily standups have been the most useful development I've seen in my 17 year career so far, I'm not sure why there's the hate for them.
It's a small time allotment where everyone gets just a couple of minutes to sum up where they were yesterday, where they're going today and what's holding them up.
I've seen them go wrong, when managers decide that they need to attend and use part of the meeting for "management announcements". I've seen it go wrong when one team member cannot shut up and regularly took over the whole meeting (yes, the scrum master was ineffectual). But in general I've found the daily rapid-fire catchup a thing of beauty.
The rest I can take or leave. One of the worst projects I've ever observed had a highly paid SCRUM Master/Consultant/Trainer and that team seemed to spend several hours each day on process. They failed to deliver anything, ever, the product was scrapped and everyone was laid off, including the development manager.
- flukus 10y ago> It's a small time allotment where everyone gets just a couple of minutes to sum up where they were yesterday, where they're going today and what's holding them up. Don't you have a kanban board or equivalent where you can see what everyone's been up to and what their upcoming tasks are? Do you need to know what's holding them up if it's not you? For those of us complaining, it's not that we don't see the value, we just see other, arguably better ways to get the same value.
- Nursie 10y ago>>Don't you have a kanban board or equivalent where you can see what everyone's been up to and what their upcoming tasks are? Not where I am now, and in places where we have had various boards it was still useful to have the quick verbal communication - "Oh, I have a script that deals with some of that, it might be a useful guide, let's talk afterwards" >> Do you need to know what's holding them up if it's not you? The same thing may bite me soon so I need to know, or I may have a simple workaround and can offer to help them out. I find the line in the article about it being unnecessary if the team is functioning and communicating well quite weird - the stand-up, in my experience, has been a part of that and has also been a way of saving other communication time.
- dasmoth 10y agoDaily standups have been the most useful development I've seen in my 17 year career so far, I'm not sure why there's the hate for them. Two things that bother me: 1) You either have to hold them at the start of the working day (in which case they become a synchronization point and everyone has to turn up at the same time -- which will inevitable be a bad time for some people) or a bit later (in which case you end up with an odd slot at the start of the day which usually isn't long enough to start on anything substantive). 2) They mandate daily visibility, and (by design, I think) prevent people going off for a week or two and solving something substantial on their own. There are possible solution to (1) -- e.g. asynchronous stand ups in a chat client (and it's probably not coincidental that the only times I've found these things at all helpful, they've followed this model rather than the actual stand-up-in-circle thing). But (2) is kind-of the whole premise of "agile teams", so not sure what can be done about that.
- Nursie 10y agoDoes the timing matter? We hokd ours in the middle of the day at the moment. Still seems to work (though the discipline is lacking and they often overrun, which I hate)
- dasmoth 10y agoIt matters if you're trying to preserve some decent chunks of time for focussed work. And if matters if the standup is scheduled for 9am and you can't drop the kids of and be sure of getting in before 9.10 If everyone goes for lunch at the same time, holding it 10 minutes before lunchtime could be a smart move. But only if you've already got that "everyone eats together" culture.
- Nursie 10y agoWe hold ours after lunch. No "everyone eats together culture", unfortunately, but there is now an "everyone finishes lunch by 13.30" culture.
- humanrebar 10y ago> asynchronous stand ups in a chat client I've been thinking this is actually the perfect standup. People don't tend to write novels in chat clients anyway (and to the extent they do, you can move the text to a README or wiki and just link it). Does anyone have any experience with this? Any pros and cons worth mentioning?
- humanrebar 10y ago> ...everyone gets just a couple of minutes to sum up where they were yesterday, where they're going today and what's holding them up. Peer-to-peer, listing blockers is more or less the only thing that matters, followed distantly by making sure we're not stepping on each other (deploying the same thing, refactoring the same class). It's also important to sync up that designs are good and work together, but that's outside the scope of Agile (and standups). The bulk of the info in the yesterday-today-blockers standup is to let the manager get a quick rundown of what the employees are up to. It's a management tool, basically. And that info is all duplicated (if you're doing it correctly) in the agile board, the burndown chart, and in the version control system. So management could just create better queries and dashboards on top of existing data and get the same information.
- Nursie 10y agoWe've run the standups like that with no management involvement at all in some places. I still find them useful as they allow people to resolve dependencies a schedule work appropriately. Those other tools have a tendency to get ignored, get out of sync, out of date and add overhead.
- humanrebar 10y ago> Those other tools have a tendency to get ignored... That's basically my point. Managers should home their craft and improve their tools instead of molding the people around them to meet the needs of middle management.
- Nursie 10y agoWell, I'm not sure that the daily standups have always been about that, and as a developer I've found them useful.
- humanrebar 10y agoI've found them useful, but only to the extent that they focus on burndown and not presenting status reports to management while the rest of the team listens.
- valuearb 10y agoI had a standup at a 24 person company where every single person (except the CEO of course) had to attend standup and report. That's a long standup, esp. when someones report spirals into a discussion. Wasn't very agile.
- Nursie 10y agoYeah, that sucks, you don't want more than 5 or 6 people in one really.
- overgard 10y agoMaybe its useful to you, but to be honest, I cant remember a single thing about the standup meeting I had today and I made a point of paying attention. People talk about like "blockers", but if something is blocking me I just go talk to whoever can fix that, and if I need to know about something I just ask people to loop me in. I dont need agile for basic communication skills
- Nursie 10y agoYou don't need to remember what happened this morning particularly, so long as you participated. Great for blockers you know how to fix or who to ask, but you may miss some others. "I need permissions on this server to do X and am waiting for someone to do that" might have an easy workaround that a colleague knows. "I'm doing X but it's taking some time because I'm not familiar with Y" might be met with someone offering to help as they have experience you didn't know about. You'd never get this without some form of generalised conversation.
- overgard 10y agoI feel like I can get all of the things you mentioned without a mandatory daily meeting, either through slack, email, or just conversing with someone. It's not that the daily standup bothers me per se, but lets calculate this out for a second. If the daily standup eats about 15 minutes, and you work about 250 days a year, thats about 3500 minutes spent in a scrum. Considering that, even being charitable, I might hear one useful thing every two weeks... I kinda would rather spend those 3500 minutes elsewhere