this post was submitted on 17 Aug 2023
16 points (100.0% liked)

Programmer Humor

32380 readers
1315 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
[email protected]
[email protected]
16
Very unpopular opinion I think (feddit.de)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
33 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (2 children)

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.

[–] [email protected] 2 points 1 year ago
  1. I will never again act as scrum master if I can help it.

Is why I joke that there are no SCRUM masters. Anecdotally, most of those I've met who were great at SCRUM mastering noped out of it within a year. It's like physics abhors a great SCRUM master.

I'm currently assigning all of those responsibilities to the development manager and to the development team leads. That's at least working without causing me to lose people.

[–] [email protected] -1 points 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.