3 ms·

If agile isn't dead, why is it still not working?

• bitwize 2y ago
  Milt Bryce described Agile perfectly in 1982: "Do a superficial feasibility study, do some quick and dirty systems design, spend a lot of time in programming, install prematurely so you can irritate the users sooner, and then keep working on it till you get something accomplished." https://m.youtube.com/watch?v=SoidPevZ7zs&t=47m32s https://m.youtube.com/watch?v=SoidPevZ7zs&t=47m32s Programming is only one small piece of the puzzle -- according to Bryce only 15% of the work. You need to do extensive systems analysis and design -- identifying what the informational needs are of that piece of the business and designing a system that will provide them -- before writing a single line of code. Agile doesn't work because in Agile, management has abdicated responsibility to the programmers, and programmers don't understand the business. We've fallen so far that Agile takes it as a given that requirements are so vague that they're completely unknowable a priori -- in other words system requirements are completely indeterminate quantum values that can only be fixed by "observing" them, by hacking up a rough system, throwing it to the users to be irritated by, collecting their feedback, and trying again. This is false, of course, but what's needed is a structured, comprehensive approach to requirements elicitation and systems design. Once that happens, coding becomes mere translation.
• taylodl 2y ago
  [flagged]
  • deleted 2y ago
    [deleted]