• ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    My experience is that doing a touch base once a week is sufficient for identifying issues, also it’s not like people can’t communicate directly with each other when they’re stuck. If people aren’t being proactive about that without having to have a daily stand up that sounds like a team culture problem.

    • folkrav@lemmy.ca
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 month ago

      I too had those hour long snoozefests where 99% of what’s said doesn’t pertain to my work, and those useless meetings that could have been a message on a Slack channel. I still feel like the sentiment is a very broad generalization based on some assumptions that may or may not apply well to every work environment.

      My most recent project has direct dependencies between 5 teams just on the developer side, and multiple internal and external clients. Figuring out if we need to reach out to the stakeholders or figuring out who can help them on a particular task isn’t necessarily always that straightforward, depending on scope.

      Anecdotally, the devs on my team were losing a lot of their time doing all that stuff before I joined as a tech lead in August. I spend most of my non-dev time (about 50% of my time, lately) shielding the rest of the team from stakeholders, pushing back when needed, pushing back on various demands, enabling communication lines, all to protect them from context switching and let them code.

      And honestly… Outside all that, agreeing with me or not, is 15 minutes of human interaction that terrible lol?