TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Scrum will die Scrum was successful in the past, but its time is over

11 pointsby benkanalmost 2 years ago

3 comments

Raidionalmost 2 years ago
I used to be a diehard scrum advocate (though I&#x27;ve always been focused on results and not just process as magic). I&#x27;ve felt in my latest role, scrum doesn&#x27;t cut it.<p>Problems: - Larger team: I can&#x27;t swarm developers on a single project. It&#x27;s impractical for every team member to be instantly able to help out with the domain specific work. - We&#x27;re a platform team and so are in the way of $FEATURE a lot. Our long term roadmap is primarily driven by other teams urgency and we have to roll with it. - Estimates are a boolean, not a date. Our estimates don&#x27;t matter because unless it&#x27;s a 6m+ project, it needs to be done because of $FEATURE<p>Because of this, sprint planning is never stable long term. Every work comes with tradeoffs being made at the top level. Estimation means time away from doing work we know we&#x27;re going to do unless it&#x27;s a huge SWAG.<p>I like the ownership scrum has, but the work is gonna take what the work takes. Why should we spend tons of time estimating and planning when we just need to get the work done before next product launch 6m out? Feels like Kanban might work better. I need to read up on the Basecamp model.
nivertechalmost 2 years ago
Scrum was invented to manage a team of dysfunctional COBOL programmers at a bank. That says it all about it.<p>It&#x27;s mostly for less skilled and unmotivated workers working on a relatively simple projects (e.g. corporate&#x2F;enterprise software development).<p>Leaving aside stupid rituals and ceremonies, which are time-wasters, and motivation-killers. Scrum aims to address the task management aspect by approaching it as a tickets bin packing problem. However, it relies on the false assumption that accurate task estimation is possible.<p>For reactive or unplanned work, short sprints can be effectively replaced by a pure Kanban approach.<p>For proactive or planned work, long sprints can be better substituted with mini-waterfall SDLCs.<p>While the post mentions the Shape Up method and highlights that FAANG companies do not use Scrum, it fails to mention that these companies utilize mini-waterfall SDLCs with approximately six-week cycles.
评论 #36171131 未加载
sharemywinalmost 2 years ago
Sounds like the author is advocating for Chaos?
评论 #36169886 未加载