Can you please activate your webcams?

Please choose a sticky note color to use for this meeting

Please take one of these smiley stickers and tell the others how you feel now

  • 👍Maximum Derek👍@discuss.tchncs.deEnglish
    10·
    1 year ago

    Having worked in a lot of scrum teams in positions ranging from Jr Dev to CTO, I have become a huge proponent of scrum masters.

    1. The scrum setup is that way for a reason. The Stake Holders speak for the company, the devs speak for the infrastructure, the Scrum Master speaks for the process, and the PO is also there. And none do each others speaking jobs well. The process of scrum will tend to drift back toward dev burnout without a good SM.
    2. Devs shouldn’t be spending their time managing tickets, we should be developing. Backlog grooming, sprint ready ticket reviews, fighting with POs, stake holders, and Support, and fretting about velocity should be left to the scrum master.
    3. I will never again act as scrum master if I can help it.

    And in my experience a SM becomes a full time position at about 15 devs.

    • Scrubbles@poptalk.scrubbles.techEnglish
      3·
      1 year ago

      Exactly right, scrummasters should be outside of the business and developer chain so they can uphold the process first and foremost. One of the phrases I hate the most is “we’re in crunch time, we don’t have time for process.” No, that’s when you need process the most! It doesn’t matter if it’s crunch time or whatever, PMs and business sometimes needs a reality check on what is possible and what isn’t, and developers need someone in their corner that isn’t also their manager.

    • vlad@lemmy.sdf.org
      31·
      1 year ago

      From all of the replies it was to me that a Scrum Master can be very useful in specific projects that involve interplay between many departments. But in reality it seems like it’s a way for companies to avoid creating clear job requirements.