• by apothegm on 12/16/2024, 9:45:59 PM

    Historically a ridiculous percentage of software projects either failed entirely or suffered massive overruns.

    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.

    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.

    Then everyone else cargo cults and copies whoever looks like they know what they’re doing.

  • by dtagames on 12/16/2024, 11:32:23 PM

    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.

    Because scrum aligns with the way managers think and produces output they like, it gets ordered into existence. It doesn't align with developer methods nor produce what devs want (working code), so therein lies the rub.