Hacker News Reader

Comment by nprateem | Hacker News Reader

IME it's just scrum masters trying to prove their worth. Since they're either non-technical or not close to the tech, they're reduced to robots asking "do you need me to escalate that?", or "so can we move it to done?". I'm sure most scrum masters could be replaced by chatbots.

It really gets quite tiresome, especially since if I needed something escalating I'd have asked them already, and I'm perfectly capable of moving a ticket myself.

Instead I just disengage for the hour and half of standups I have per day (yes, I know)

View on HN

I don't understand hiring scrum master as a full time employee from my experience it always is role for one person in the team that does other stuff full time.

I never saw scrum master who is doing only scrum stuff myself but from what I read on the internet there are people who saw it.

Scrum masters are one of the reasons I chose to be overemployed. Their presence in an organization taught me that it is highly rational to be performative over performing.

How’s it working out for you?

Rule 1.

Do you also have scrum-of-scrums? Because that is out DevOps team's latest idea to speed up an ERP project. So we get scrum masters instead of functional ERP experts and consultants. I am curious so, what a scrum-scrum would actually look like...

> Do you also have scrum-of-scrums?

I remember my previous employer trying that out in one or two departments. Ultimately that company landed on SAFe Agile and it was a complete and utter shit show.

Where I'm at now is "doing" Kanban but the standup is really just a daily status update. I'm slowly getting the management to recognize that these things are problems, why they are problems, and what can be done about them. But I'm much happier with this situation because I can actually push back against it and try to improve the thing. At my previous employer, any attempt to even begin highlighting problems would render you standing alone against what amounts to a committee of management (in this case, specifically, people who are only employed because of the fact that they use these extremely heavy processes) if you wanted to discuss these things.

Your previous employer sounds a lot like my current one. Add to that a DevOps head who currently holds his first job in anything IT related and actual developers that are almost exclusively external and subcontractors... All our internal developers are doing is Palantir dashboards and some interfaces to get the data into Palantir.

Scrum of scrum doesn’t work, you shouldn’t have a separate “devops team”. If you really must, someone from that team should sit in your scrum to link back to their team any blockers.

Otherwise what you have, and I’ve seen this in multiple places, is developers getting blocked by DevOps constantly, so basically setting up “shadow” infrastructure to try and work around the problem.

Reply on news.ycombinator.com