12 ms·
One thing I don't like about standups is that they can create a false sense of either blockage or someone being ineffective at their job. For instance, there h
by ravenstine 8y ago
One thing I don't like about standups is that they can create a false sense of either blockage or someone being ineffective at their job. For instance, there have been many times where I've worked on a task or a set or related tasks for weeks or months, simply because the tasks required a lot of forethought and careful planning. There were times I somewhat dreaded standups because I knew that I'd say that I'm doing the same thing I'd been doing for the last several days, like a broken record. I don't want to have to say "Yup, still workin' on those bugs" every morning. When shit's fixed or I've completed a feature, I'll let you know.
In fact, all I like about standups is seeing my team mates once a day. Besides that, there's almost no upside. Literally everyone can read the project board to see what we're up to. If you're really so curious as to what everyone is doing, why not just look at that?
- w0m 8y agoSounds like your project is scoped too broadly for daily standup then, though sometimes model just doesn't fit the task and you get the above.
- kolinko 8y agoBesides that, I hate that they took me out of rhytm of work. If a standup is at 10am, and I arrive at 9am to do dev work, there is very little I can do before being interrupted - I need at least 2-4h of interrupted time to do some good work.
- pletnes 8y agoStandup just before lunch might work better. That’s my experience.
- justaguyhere 8y agoIn my team, we have it early in the morning, so we can overlap with India. Folks in US have rest of their day for work, whereas folks in India do the standup at the end of the day just before going home.
- dmitrygr 8y agoMust be terrible for those in your team who aren't predisposed to waking early
- leggomylibro 8y agoIt works very poorly in practice, in my experience. You interrupt people 2-4 hours into their work, which is highly disruptive for those who get the most done in the morning. Often discussions run on past many peoples' lunch time, which can make people cranky and occasionally leads to tense exchanges which might have been more amicable if people weren't hangry. You wind up with people melding the work they did during the previous day and the current day. It gets difficult to keep track of what you did between two days' midpoints compared to what you did during a day. And things get worse as more items are inevitably added to the standup meetings (now we need to check on tests, now we need to add a review of open tickets, now we need to involve people from other teams, etc). In my experience, pre-lunch scrums result in heavy disruption and a bunch of people who feel like they could be doing other things to much greater effect.
- Shaanie 8y agoIf you're not keeping the daily scrum shorter than 15 minutes then that's in and of itself a problem that will make people annoyed and disrupted.
- isbvhodnvemrwvn 8y agoThe problem probably isn't the time the meeting takes, it's the subsequent discussions about various things brought up during the meeting.
- losteric 8y agoMy team just does "asynchronous stand-ups" - share your status once day in a dedicated Slack channel, whenever you want. We do this on top of a good culture of asking for help and posting regular updates on our internal Sprint tracker, it works quite well.
- RussianCow 8y agoI think this is the correct way to do standups for most teams. It's asynchronous and non-intrusive, and there generally isn't any benefit from doing the standup in person anyway (aside from seeing people's faces if your team is remote).
- JustMatthew 8y agoFor technical or non-technical teams, this is usually all that's needed. If there are any questions, they can be addressed below in a reply thread or via a call or face-to-face. It's amazing how much of a time saver and efficiency builder that can be. It's equally amazing how many managers prefer time wasting group meetings where people essentially read written reports...
- somethingsimple 8y agoBeen advocating this for months at my company with no success. Our standup is of the worst kind: conference call.
- walshemj 8y agoThat's why you should do them at the end of the day as we did of my first very successful Agile project - presented at the IIIE I believe after we finished. Though that was the full on clean room high level sponsor route, collocated with the customer.
- Jach 8y agoI did that (4pm standups) for a while on a team that was just me and another guy plus our team's dev manager, qe manager, and product manager. All the managers were in HQ, my teammate and I were in separate remote offices, so it was done over Hangouts. We loved it being late and got a lot done for just two of us over the few months, but the managers didn't like it (very few times they'd all show up, and dev manager always showed up while on a bart train) and killed it (back to 10am meetings) a few weeks before the team dissolved. I've been on 11am standups lately and they're not too bad, but it incentivizes me to either come in at 8 or come in at 10-10:30. The latter is what usually happens.
- cyrux004 8y agoWe have it right before lunch
- patmcc 8y ago>>In fact, all I like about standups is seeing my team mates once a day. Yeah, I think a better way to do standups is a couple minutes of social time, and "anybody finish anything? any blockers?" rather than going person-by-person.
- sidlls 8y agoI've run my team's stand-ups for several years now. I find without going person by person there is less communication. I still restrict each person's comments to blockers and their agenda for the time until the next standup (not daily). It's not uncommon for "no blockers, tickets X, Y, Z for next day or two" to be it for a report. It's not common but occasionally this will remind someone else of a blocker they have which they can chime in with during their update or else at the end if they've already gone.
- rickyc091 8y agoAgreed with this. I'm actually curious what level of engineers Jason is leading. If it's a group of senior engineers, I'd imagine everyone already knows what's expected of them, but a group of junior engineers might be a different story.
- matthewmacleod 8y agorather than going person-by-person. Better still for us has been going task-by-task rather than person-by-person. Look at everything which is in progress, get a quick update on it, move on. Five minutes tops, everybody is up-to-date, issues flagged.
- Sharlin 8y agoYes! At my last workplace we switched from person-to-person to task-to-task and it worked great.
- deleted 8y ago[deleted]
- matthewmacleod 8y agoFor instance, there have been many times where I've worked on a task or a set or related tasks for weeks or months, simply because the tasks required a lot of forethought and careful planning. That would raise immediate, massive, flashing red alarm bells in my teams! I understand that different environments have different requirements, and different teams have different needs though.
- ravenstine 8y agoMaybe other teams work radically differently, but everywhere I worked it was inevitable that team members would occasionally get "meaty" projects to work on where they would take primary ownership. Under the repetitiousness and time constraint of stand-ups, it still outwardly appear that the smaller tasks broken out of a large project can all sound the same to others on the team who are only mildly interested in the details of other people's tasks. If I was working on a very functional team where we had the employees and resources to work very collaboratively across projects, I'd certainly agree that (groups of) tasks that take that long should raise alarm bells. But most companies, in my experience thusfar, minimally value their developers and only hire X amount of them, so the developers they did hire are naturally forced to take on large projects to the point of taking sole ownership of them. Disregarding that, I don't see it as unreasonable that tasks shared between multiple people would take weeks to figure out. If I were hiring developers, I wouldn't want them to race to make a bunch of horseshit that's going to fail, but instead they should take their time to figure out the right approach. In conjunction, they should be able and allowed to communicate when long-running tasks aren't going anywhere, without any shame. As long as they document the steps they took along the way, there's no reason that standup needs to play a role; with documentation, a manager should be able to tell if an employee is incompetent or merely trying to do their job right. I don't think that stand-ups are really a big deal, but if I were running a team, I probably wouldn't use stand-ups in a traditional sense. Rather, I'd keep stand-ups but not make them goal-oriented or strictly related to work in any sense. As I said earlier, I think it's positive for people on a team to interact at least once throughout the day if they are in the office, and a quick and optional stand-up in the morning would be a great way to facilitate this. If someone wants to bring up an issue or asks if another team member knows how to do X thing, then awesome. In fact, I suspect people would be more comfortable in doing so if they aren't wasting time thinking up how to summarize their work for stand-up, and if stand-up was kept casual and didn't devolve into employees reporting to their manager.
- chomp 8y ago"working on bugs" is not a great update, it's opaque and doesn't help your team or your leader get a picture of what you're struggling with. "I tried this and this and measured this latency from the application and suspect it's a race condition, I checked this code and feel like I'm on the right track, and if someone wants to take a second set of eyes on my bug I would appreciate it" is a much much better update. Stand ups are about communication with your peers. Having to hunt down tasks you're working on and reading through each task can create an unnecessary mental load that can be solved with a single 1 minute "ESPN sportscenter edition" summary of your current issues. However, blockers do create a sense of ineffectiveness. Especially on small workload teams where task swarming doesn't net too much benefit. "Hey I am still waiting on $vendor to configure their service" or "Still waiting on netops to tag $port for vlan blah" or "Procurement put in a PO for $hardware, still waiting on it", there are times when we are waiting for something, and there's nothing able to be done currently. Especially when the immediate tasks are already doled out and your leader doesn't want to pull more work into the current sprint. Subsequent tasks could be too large or complex to be pulled in. Current tasks could be unable to be broken up any further, to which I have to say, pair program until your blockers dissipate. We do this at my current job, and it really creates tangible benefit. As for TFA's bulletpoints on why sprints can be bad, most of their arguments are bunk except for this one: > 4. Extroverts thrive at stand-ups, planning, and retros. Not everyone is great at self-selling, and people who move up in the company are the ones who hype their personal brand, not necessarily those who are the best at their roles. I don't know how to solve this as it's a personality issue, but I do think it can be a problem for a lot of businesses and teams.
- ahelwer 8y agoThat's useless because everybody else tunes out. Nobody cares what debugging methods you tried on some project they've never touched. If you need help you can just ask somebody.
- chomp 8y agoI think that's either a team culture issue, a management issue, or a business culture issue. Teams I've worked on have had no issue brainstorming ideas for a person who's stumped. Now, I'm not totally defending standups here, I've been on teams where daily standups are a stuffy formality, and they are miserable. I've also had the pleasure of being on teams where weekly standups were implemented, and they were an absolute delight and completely useful. I will qualify all of my opinions with the fact that the best teams I've worked with implement Kanban, so there is no sprint planning. We just pull off backlog and work with weekly standups. There's way way less overhead, with some tradeoffs. I also definitely think that certain team cultures are completely incompatible with standups, to the point that you receive negative benefit from implementing them. If you have a lot of people who are of the type "my responsibility ends where my story points end", I am pretty sure you will end up have a bad time doing standups.
- btilly 8y agoThe one thing that I like about standups is that they make real blockage or ineffectiveness more visible. It is true in theory that you can get the same thing from just scanning the project board every day. But people don't actually do it. Furthermore if you're stuck on X, standups are a perfect time for someone who was about to look for a ticket to take one off of you that they are better suited to handling. Are they perfect? No. There are definitely false positives. But the ratio of real positive to false one is good enough that they provide real value overall.
- gav 8y ago> there have been many times where I've worked on a task or a set or related tasks for weeks or months, simply because the tasks required a lot of forethought and careful planning. The idea of standups and breaking down work into chunks that fit in a short sprint is to avoid this sort of situation where somebody is off on their own and not getting feedback. I find that people are overly optimistic about their chances of getting a task completed in the promised time frame. If something is expected to take five days, I'll hear every day that it's going well, right up to the last day, then all of a sudden it's not going to be done. The more granular the task is, the easier it is to deal with slippage because you get to know about that slippage sooner.
- BigJono 8y agoA task should be something that can be done independently by one person. Sometimes you have a big chunk of work that's tightly coupled and can take months to implement, how do you best track that? In my experience what happens is one of three things: (a) You try and bring multiple people into that feature and it turns into a clusterfuck of awful merge conflicts and hours upon hours wasted on co-ordination instead of building (b) You track it as a lot of tasks (~30-50), and whoever is working on it spends half their day fielding questions like "Can I pick up that task for you?" or "why are all the highest priority tasks assigned to the same person?" (c) You track it as one or a small number of tasks (~2-5), and whoever is working on it has the problem GP mentioned with stand-ups, where they don't have anything granular enough to report and end up looking like an incompetent tool. I've experienced all 3 and they all suck. I'm not convinced that option (c) isn't the furthest down the right track. Option (a) can be a horror show and probably one of the quickest ways to lose a good dev, option (b) can work but it's dependent on a manager that understands the work and isn't going to lambast the dev for blocking up the backlog with self-assigned tasks. Option (c) just relies on adjusting or removing stand-ups to not focus so heavy on day-to-day progress.
- gav 8y agoI struggle to think of an example where I'd ever let somebody go off and work on something for months. I can't think of how they would be successful, let alone take on the risk that they quit or get hit by a bus and nobody can continue the work.
- paulsutter 8y agoThe best meeting updates are just the surpises. Sometimes I’d start meetings with, “first, let’s go around the table and report any surprises this week”, and then adjourn the meeting.
- majormajor 8y agoI have other issues with standups, but if your concern is "I don't look productive and I don't want to talk about what I'm doing" not having standups isn't going to make you look more productive. If you're working heads-down for weeks or months without standups, people are still likely to wonder if you're stuck/ineffective/blocked if you're not communicating in more detail than "it's still in progress."
- taeric 8y agoI think the desire is more to have goals and work towards those. If you don't have daily goals, then having a daily standup is going to be pointless. That is, if I am working for weeks or months without making visible progress, but I have successfully delivered the last X things on time, why are you worried about what I look like? So, yes, people should grow into longer timelines that they can appear to be slacking off. I expect the tasks we've given the newest intern, as an example, to be something that can show daily progress. In large, because it will likely need daily coaching. As you get on the larger projects, though, asking me to break everything down to daily chunks is itself a chore that may add significantly to effort. Worse, it encourages people to fall for the sunken costs fallacy. If you burned down all of that effort, many folks are hesitant to take any of it back. If I haven't let you know about the small progress I made on the last experiment I did, then I am as likely to abandon the path and try something else if I am confident it will be better.
- majormajor 8y ago> That is, if I am working for weeks or months without making visible progress, but I have successfully delivered the last X things on time, why are you worried about what I look like? I'm not worried what the OP looks like, or generally what I look like for that matter, but they were worried what they look like. I just dispute the claim that standups are the root of their anxiety about that.
- taeric 8y agoI think it is fair to think you will be measured with the same general yardsticks that your peers are measured by. So, if you are in a standup where others are giving daily task reports, it is natural to expect you should. And that if you are not, it is natural to feel something is amiss.
- hw 8y agoWhether standups are useless or not depends on the dynamics of the team. With the team I'm currently working in there are no standups, all communication is async and everyone knows what everyone else is working on. If there's a problem, holler in chat, or discuss IRL. There's also the project board where anyone can just hop in to see progress. There is a trust in each other in my team, which is not something I can say for other teams I've been with. The whole agile methodology shouldn't be taken as is. Standups, sprint planning, retro etc all can be ala-carted with modifications depending on what type of team you're in and the people in it. The ideal scenario is that the team is a well-oiled machine, much like a precision, well built watch. No standups or meetings that force context switches and interruptions. Adapt to the team. Do away with unnecessary processes. Just because standups are done everywhere doesn't mean you have to do it just for the sake of 'following the process'. It also doesn't mean you should do away with it, if you have a team that's new, or if there's a lack of communication or trust in each other. Isn't the point of agile, to be agile in everything that we do, including the agile processes themselves?
- walshemj 8y agoThen that is a project that should not use Agile in my opinion.
- ravenstine 8y agoI first read your comment as the inevitable "that's not true agile" response. Haha Perhaps companies should just pick and choose what parts of Agile methodology suits the situation. I don't really buy the idea that Agile only works if there's an ensemble effect from every workflow aspect made Agile.
- speby 8y ago"still workin' on those bugs" is really pretty useless. I'm not suggesting you're not a disciplined person but at some point, debugging something for days on end is a sign you may need some help, a fresh set of eyes, or come up for air and re-group. Same goes for feature development. If a single user story representing a whole feature (or part of a larger one) goes on and on and on, that's either a sign you perhaps rabbit-holed it too deeply, need some help from another team member, or need to raise a flag and split the story into another piece, possibly even one someone else can rally around to help close it.
- somethingsimple 8y agoI wish everything was so simple. At a past job a very technically strong coworker spent months on a problem and eventually threw the towel and handed it to me. It took me another couple months to find a reasonable solution to it. Some problems are _really_ hard and no amount of help will get a dev to solve it faster.
- djsumdog 8y agoBut if I hire nine women, I can get a baby in a month right?
- duxup 8y agoAs a n00b just getting into software development this might be a dumb question but does saying "Yup, still workin' on those bugs" really create a sense of blockage or such? I gotta think that's kinda a common thing to be said and other devs would understand that that happens...
- merlincorey 8y agoThe problem is that product managers and management in general want features and don't care about technical debt. So if you are working on a bug (fixing technical debt) then you are not working on a feature. Also, working on features is often (but not always) more predictable in time estimation than working on bugs, which can be a completely exploratory task with the only endpoint being "it works now"...
- Falkon1313 8y agoIf working on the same ones, then after a few days, yes. By then you should have explored some debugging techniques, options for solution, etc., and either can't figure out how to replicate or debug it or have found a tricky bug and 1-3 ideas for a solution, but all the potential solutions seem bad. That's when you can say you're blocked, ask the team for ideas on how else to replicate/debug, or try to get consensus for the least-worst hacky fix that you've come up with, or any other ideas based on what you've found. We all spin our wheels or get stuck sometimes, so of course we understand, and that's exactly what it's for. But you have to give that context and say where you're stuck.
- JJMcJ 8y agoSome standups the boss gives off an unpleasant vibe than nothing should ever take more than a day. Get stuck on something for a few days, and it feels like it's time for a new job.
- bitwize 8y ago> I don't want to have to say "Yup, still workin' on those bugs" every morning. Then don't. Give specifics about what you did, what you accomplished or didn't accomplish, and what your next steps are. Provide evidence of forward velocity, or ask for help if you're stuck. The key here is accountability. Don't be "the guy in a room" who doesn't apprise the team of what's going on in his world. That guy is first in line to be fired.
- ravenstine 8y agoI find it interesting how literal people took that. Must I have provided a lengthy, detailed example of what I would say at a standup? I'm the guy who pushed for people to provide more detail at standup. I thought I'd communicated my point and didn't think it a particularly good use of my time or anyone else's to spend more time on that sentence. Now I regret writing that it at all. If anyone manages to read this, keep in mind that I was not suggesting that a professional update along the lines of "d'uhhh... i did a thing" is particularly valid.
- eeeeeeeeeeeee 8y agoThis is especially true if you're working on a research task, or the research portion prior to really driving in and implementing the feature. Every day you're basically saying the same thing and it looks like you're struggling, but you're mostly just learning.
- grappler 8y agoI hate it because every approaching standing meeting feels like an approaching "rejustify your existence" checkin. Even if I'm not going to be judged out loud in this meeting, I'm going to have to explain myself. I have a problem in front of me that I'm working to solve. Maybe I decided to do some reading about possible ways to solve it. Maybe I decided to learn one of the tools that I'll probably use in the course of solving it. Maybe I'll try a particular approach. Whatever I decided to do yesterday, I have to decide how to frame it and describe it today. I can practically hear another engineer or manager thinking "why didn't you just X" where X is some simple thing involving less time and thought than what I did. And I don't want to have that conversation with them right now. I am still in the middle of it. I want to be able to say in a few days, "Here's a solution! It meets the requirements and in a really elegant way if I do say so!" I live for that. I want the freedom and flexibility to get to that point without being probed every day about how I'm getting there. I used to do that, before scrums and standups took over the programming world, and it was great. Having a daily checkin robs me of that latitude. I'll gladly pick someone's brain if I want their input or feel stuck. But if I want to think outside the box a bit, a daily checkin can feel like a pretty short leash.
- collinmanderson 8y ago> In fact, all I like about standups is seeing my team mates once a day This may sound a little funny, but at my work we do daily morning prayer from 9-9:30am (company-wide, 20-25 people). We sing a few songs with guitar, then talk about our weekend or personal life, or whatever. Some days it's more work related than others. Maybe we'll share a little about what we're working on, or bigger updates from managers, but it's definitely not a planning meeting. It's awesome.