@wft said in Is DevOps also a manifestation of white male privilege?:
But even such blokes are far more productive if you don’t put them in more meetings where they would fuck ants even more. For chrissake.
Not necessarily. There are parts of scrum that do work, but some developers think they're above that. "My job is writing code, not talking to product owner." No, you fucker. Your job is to deliver the best fucking product. This means you need to talk to the people who understand the business, so you can understand the business and write the correct feature without wasting time.
"My job is to write code, not seating for 2 hours and trying to figure out how long tasks will take." No, you fucker. Your job is to deliver on time. So sit the fuck down and figure out what "on time means." If you fail to do that, you'll piss off the business and they'll make you feel that.
My point is, a lot of Devs don't want take the responsibility for the product and the process. They think they're above that, cause they're not managers, they're only there to write code, according to a spec that someone else created. The problem is, if you give away the control of the process to non-devs, the part that matter to you won't be executed as well as they could have if only you bothered to take part. The spec will be vague, timelines unrealistic, feature won't work as desired.
I'm not saying that scrum as designed and sold by consultants will work everywhere in an unchanged manner. I'm saying that it tries to change the view that devs have in what's their profession, brings them closer to the clean coder-style professionalism by insisting on discipline.
It's a powerful tool, but sure, if used in a wrong way, it'll blow up.