The Death of Scrum – Built for a slower world, performed by those who left
1–10 of 51 posts
Re: The Death of Scrum – Built for a slower world, performed by those who left
#2“Interactive obituary - 22 min”
Ugh is there a regular text version I can read at my own pace?
Also why light text on black background? Hurts my eyes and is very difficult to read.
Guess I’ll wait for someone with more patience and better eyesight to maybe provide a summary or something :)
Re: The Death of Scrum – Built for a slower world, performed by those who left
#3> This essay is not a hot take. It is an autopsy.
This essay is AI slop with a fancy website design.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#4“We hold a meeting to talk about the meetings, and another to plan the meetings about the meetings.“
I dropped scrum last year.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#5“Interactive obituary - 22 min” Ugh is there a regular text version I can read at my own pace? Also why light text on black background? Hurts my eyes and is very difficult to read. Guess I’ll wait for someone with more patience and better eyesight to maybe provide a summary or something :)
Yeah, this seems like it could have been a few paragraphs. It goes on and on.
I’ll give my hot take without reading.
I’ve been in a lot of kinds of scrum and it seems like a YMMV thing. The most effective scrums are the ones which start from first principle and create a process for the teams current needs.
Many of the most effective ones worked out of a spreadsheet or Google doc rather than an issue tracker. Sometime the PM would update the issue tracker behind the scenes to keep devs out of it.
Anyways, my point is that most effective things are custom built rather than trying to apply a blanket process across a company or to different situations.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#6My favorite scrum story: When I worked at reddit, we were still owned by Condé Nast, and we worked in the corner of the Wired magazine office. Condé Nast got a new CTO, who was completely all-in on agile. To the point that she called everyone into a conference room to read us the agile manifesto word for word.
We then went back to our little corner conference room and continued to build things in an agile way, like we had been doing for years, without all the meetings.
The poor Wired folks suffered a worser fate, and had to have all the meetings.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#7“Interactive obituary - 22 min” Ugh is there a regular text version I can read at my own pace? Also why light text on black background? Hurts my eyes and is very difficult to read. Guess I’ll wait for someone with more patience and better eyesight to maybe provide a summary or something :)
Mobile safari reader view fails too with this layout / style.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#8So an author whose company sells AI tools to organizations has published an AI-written sensationalist website detailing how horrible the "old way" of doing things is, in the hope that more people will pay them for their "new way" products. Wow, color me shocked.
Re: The Death of Scrum – Built for a slower world, performed by those who left
#9I think I like this article and I haven't finished it yet, but I don't think the bottleneck has shifted to non-human with the advent of agentic AI. It's still the human (deciding what product direction to take, reviewing code, etc)
Re: The Death of Scrum – Built for a slower world, performed by those who left
#10I've been hoping for a paradigm shift away from scrum for years! It was good for like 5 minutes after it replaced Waterfall and then it morphed into a freaking hellscape of grifters and non-techies invading the business space. It's never worked out, never! Some of the ceremonies are fine, but overall, it's crap. And people live it like a religion and become angry if you complain about it. It's a freaking work process, not a religion! All it did in large enterprises was become another way to bludgeon developers and take away their agency. Hmm, I recall it was supposed to be ABOUT the developers, not about JIRA and filling out all the idiotic fields in the JIRA tickets. Story points, t-shirt size estimates, RETROSPECTIVES--that never, ever, not even once, led to a positive change. All so a bunch of r/e/t/a/r/d/s who say things like "I'm not very technical, but here's what I think..." to which I always responded--"If you're not very technical, then what makes you think you can lead a technical process?" Idiots and scammers.