That phrase is so overused in light of massively over engineered solutions that are created every day in our industry . Let’s face it: this project loads some data via http and displays some text and primitives on a display. This can easily be handled on a esp32 with room to spare. But somehow we think it’s normal to involve an OS, a fully fledged computer and a browser to do this. Seriously, we need the opposite of the Knuth quote: “When in doubt don’t ship a browser” or something like that.
> But Agile to me always seemed to be about management being able to absolve itself of all responsibility for not being able to figure out what to build or how to build it and to always be able to blame the engineers.
This is Agile’s “Executive Armor Effect”, which turns developers into a sort of ablative armor that can take hits for executives.
Let me say this about agile: the most important part of a software project is the first 20% of it, when all the foundations and building blocks for the application have to be created.
What I’ve seen happening at the dozen or so different scrum places I’ve worked at is that agile abrogates this first critical 20%, and more than anything this is what makes agile so destructive to software projects.
