2 ms·
I worked for a few years in a company that did salutary scrum, which is to say that we shoehorned our developer-led process into the correct buzzwords and cargo
by logfromblammo 12y ago
I worked for a few years in a company that did salutary scrum, which is to say that we shoehorned our developer-led process into the correct buzzwords and cargo cult practices to make the management think it was Scrum. That was the best job I ever had. I was very sad that the company was purchased by a larger company with a history of annihilating their acquired development teams without thinking. (That practice actually called into existence one of their current major competitors, as an example of the Batman Effect in action.)
As a result, I didn't think Scrum was all that bad, until the worst job I ever had instituted the daily stand-up meeting.
Anecdotally, Scrum will do nothing to help an already good development process, and will make an already bad development process much, much worse.
As such, it means nothing to me if a company "uses Scrum". I have to look at the individual development teams, and see for myself how they really do their work. A decent development team can create a facade over their own working process that looks enough like Scrum that management won't interfere with it. A horrible team can create a Scrum facade over their own process that multiplies aggravation for everyone with no benefit to productivity.
I'd even go beyond "fuck Scrum" to spurn any development process that has a brand name and a dedicated consultant ecosystem.