i hate standups. i hate scrum!!

New GEDf47
Sep 4 28 Comments

are we some sort of factory workes to give a daily report of our work?? this is one reason i want to do an MBA and leave behind software development for good. anyone else feels this way?

why aren’t product managers, biz folks asked to give a daily report? they too should give a daily bs report.. what was done yesterday, what is being done today and what are blockers.... nonsense
cant standup just be collborative as in i am working on something and hey abc you might be able to help me on this

comments

Want to comment? LOG IN or SIGN UP
TOP 28 Comments
  • Uber uZ9mM
    If you do an MBA, do you think you will have to participate in more meetings or fewer?
    Sep 4 0
  • Google / R&D shadowfaz
    I hate stand-ups too but it is not that bad if done in the right way. In Google, it is fine. We just update on the bugs/features we work on for that week. But I've been in companies where we used to give hourly updates. Like this will 2.5 hrs etc. What the fcuk? It was like we were machines working with an ever-consistent output. I ran away from that company.
    Sep 4 1
    • Sumo Logic / Eng yippppe
      In my current company we have stand ups lasting more thank half an hour everyday . People give estimates like this will be done in 1 hr etc . I need to run away as far and as fast as possible .
      Sep 4
  • Google / Eng ElverG
    I haven't had a single standup since I switched teams earlier this year and it's everything I dreamed it could be.
    Sep 4 2
    • Google / R&D shadowfaz
      Which team are you in?
      Sep 4
    • Humana edjuh
      He’s not on one
      Sep 4
  • New Pino
    If it’s more than 15 minutes , it needs some moderation for sure
    Sep 4 4
    • Google / R&D shadowfaz
      It's not just about the time. It's like you have to give updates for the heck of it every single day. That sucks.
      Sep 4
    • New Pino
      Yes it does suck
      Sep 4
    • Google / R&D shadowfaz
      Sometimes I delay the work at hand to do some competitive analysis of the product or work on some proposal - just because I need a break. When I'm on the flow, I'll catch up on the missed work. But with scrums, I need to forget everything and sit and complete the work even if fatigued. That's like a machine!
      Sep 4
    • Bank of America / Product Quacky
      In a proper scrum standup you should be able to say you spent time working ona proposal and you'll focus on xyz today (even if much later)
      Sep 4
  • New GEDf47
    OP
    Mark my words there will be new companies who will abandon this practice and we will come a full circle
    Sep 4 0
  • Since you're the one doing the actual work, PMs and managers rely on these standups not only to know how things are progressing but also to remove any potential blockers from your way ahead of time. Trust me its for your and ultimately the team's benefit.
    Having said that, do propose if you have alternative ways of updating everyone what's going on and whether there are any potential blockers ahead.
    Sep 4 3
    • Google / R&D shadowfaz
      I'm fine with scrum twice a week. Are stakeholders interested in progress every single day?
      Sep 4
    • No, but they (especially sr leaders) like to go deep into whats happening and what can be improved. Without daily updates its impossible.
      Sep 4
    • Bank of America / Product Quacky
      Depends on team culture. If team is good at identifying blockers and escalating in a timely and appropriate fashion, you dont really need stand ups if you're using a system like jira or rally. Most teams suck at this and will let obstacles drag out for 2+days meaning time is lost
      Sep 4
  • Walmart qopB15
    We should have it on slack, and updates should come at whatever time employee wishes.
    Sep 4 1
    • Walmart qopB15
      Also do not attend standups physically, even if you are forced to. Just keep doing your work
      Sep 4
  • Asurion HoeR86
    You’re doing it wrong. The standup should be the team agreeing on what to get done that day and escalating anything blocked. I’ve seen many teams use it as a chance to agree on who wants to pair program on various stories as well as a chance to minimize work-in-process and focus on finishing things before starting more. There is no value in a daily status report. Things like this are what give agile and lean a bad name.
    Sep 4 0
  • Our daily stand ups are strategic. If no management at the standup then give minimal info. The days management shows up, give long list of achievements full of humblebrag.
    Sep 4 0
  • Microsoft ssMs48
    I have scrum everyday and that's really going from 20-30 min . It's more of status update to the manager than a discussion
    Sep 4 2
    • Wayfair / Eng BScK77
      As a manager, this frustrates me to no end. Nearly every team in my company does this. I try to make the point that the status is for the team members themselves. My own team does it too, so I had to skip a number of stand-ups just so they'd get into the habit. I also don't say a word until after the stand-up is done.
      Sep 4
    • Infosys / Mgmt
      TfDf00

      Infosys Mgmt

      PRE
      Ingram Micro
      BIO
      Meh.
      TfDf00more
      Ugh that sucks! My standups for teams of 10 are 10 minutes or less. It’s your chance to ask for help if needed, and call out delays or blockers. It’s NOT for management AT ALL. If I had a standup last longer than 10 minutes I’m calling interference.
      Sep 27
  • Autodesk DouP01
    Then what? Management consulting? Just join an old brand company that doesn’t do stand ups like oracle
    Sep 4 0
  • Wish t1nOne
    They do report to their stakeholders everyday based on what you say. If they’re not sharing their progress report or product plan sheet with you, ask them to and you’ll find yourself not interested at all. 🤷🏻‍♂️
    Sep 4 1
    • Google / R&D shadowfaz
      Every single day? Twice a week is fine for me.
      Sep 4
  • New
    old🧘🏽‍♂️

    New

    PRE
    Bank of America
    BIO
    Yoe: 🦏 TC: 🐐 Still not serious about life ...
    old🧘🏽‍♂️more
    Try this - instead of focusing on a team members, focus on the stories in the sprint. Go top to bottom - what needs to be done to get this story to complete. Most likely different people are working on different stories.
    First bring this up during retro, propose this as a solution - and say agile is all about experimenting (to get the buy in) and you’d want to try this for just one sprint. If it doesn’t work out, ditch it. Then ditch the company. At least you’ll know you tried.
    Sep 4 0
  • LinkedIn wallady
    Your best bet is to either speak up and change the system if you can, or just get good at playing the game, the huge waste of time that it is. Bad managers don't know how to do any better.
    Sep 4 0