TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: How did agile took over the whole industry?

4 点作者 nudpiedo5 个月前
What is the exact story on how agile, scrum and others took the whole industry?<p>Not asking about the story presented as counterpart against Waterfall or the story of its idea development from Takeuchi &amp; Nonaka or yet another well deserved criticism over its real world implementation, but how from a social and business perspective it took over the whole industry. I know it is not 100% of the companies, but most of them, and now it is even expanding to other industries.<p>Was it an incentive for management control? Did it have influencers and evangelists? Was there some tupperware scheme on selling titles and courses? just the promise of streamlined progress and predictability together with ending the contrast against the waterfall issues? was it because it is easier to pivot and adapt to change due continuous deliver? was it part of a larger atractor of rejecting long term planning, like now very few people do proper business plans and long term planning, etc?<p>Please keep it on the sociocultural and business aspect.

2 条评论

apothegm5 个月前
Historically a ridiculous percentage of software projects either failed entirely or suffered massive overruns.<p>For larger, older companies, big-A Agile consultancies were able to sell training and services by touting Agile as a way to achieve savings. They may have even succeeded to some degree at achieving a higher likelihood of eventual delivery and lower overruns.<p>Smaller companies and early stage startups wanted and needed more lightweight processes. Those that used little-a agile were more likely to succeed and grow instead of going out of business. So there’s a survivor bias at play.<p>Then everyone else cargo cults and copies whoever looks like they know what they’re doing.
评论 #42435988 未加载
dtagames5 个月前
The short answer is that it appeals to managers who are not themselves developers and believe that software can be reproduced through a factory process, like other supply chain goods. Scrum also produces lots of metrics and artifacts which these managers, lacking an understanding of code, use to judge progress and product performance.<p>Because scrum aligns with the way managers think and produces output they like, it gets ordered into existence. It doesn&#x27;t align with developer methods nor produce what devs want (working code), so therein lies the rub.