• funkless_eck@sh.itjust.works
    link
    fedilink
    arrow-up
    101
    arrow-down
    2
    ·
    3 months ago

    The purpose of stand up is to not listen to anything and say a sentence that no one listens to. It’s like a Buddhist meditation.

    • Hannes@feddit.org
      link
      fedilink
      arrow-up
      29
      arrow-down
      1
      ·
      3 months ago

      Yeah - it’s an art to find the perfect mix between “sounds complicated enough that they zone out”, “sounds like stuff gets done” and “not making people ask if you need help with that”.

    • snek_boi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      3
      ·
      edit-2
      3 months ago

      lol I hope your standups are not actually like this! The purpose is to, as a team, plan what the team will do today to achieve the Sprint goal

      • funkless_eck@sh.itjust.works
        link
        fedilink
        arrow-up
        5
        ·
        3 months ago

        I’m not actually a programmer (/engineer) I’m just a hobbyist. I work in supply chain, have worked at 4 companies in 8 years - all had stand ups, all of them are like this.

      • thanks_shakey_snake@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        Err… Is your team doing planning during standup? I’ve never heard of that, from either people who are on teams that use standups, or from any of the Agile/Scrum literature that I’ve seen. In my experience, standups are typically about either a) coordinating the execution of work that has already been committed to, or b) whoops just a status meeting and everybody’s tuned out.

        • snek_boi@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          3 months ago

          Ah, I see how my wording was confusing. I mean planning in the sense of “How will we complete the work that we already committed to?” and “What will we do today to achieve our Sprint goal?”

          I arrived at the word planning because Scrum is sometimes described as a planning-planning-feedback-feedback cycle. You plan the Sprint, you plan daily (Daily Scrums), you get feedback on your work (Sprint Review), and you get feedback on your process (Sprint Retrospective).