268% higher failure rates for Agile software projects
www.theregister.com
In praise of knowing the requirements before you start cranking out code
  • @[email protected]
    43•5 months ago
    1. Hack together a proof of concept
    2. Works well enough that management slaps a “done” sticker on it
    3. Pile of hacks becomes load bearing
    4. One or two dependencies change, the whole thing falls over
    5. Set evenings and weekends on fire to fix it
    6. Management brags about moving fast and breaking things, engineers quit and become cabbage farmers and woodworkers
    7. New graduates are hired, GOTO 1
    • @[email protected]English
      9•5 months ago

      If 2 and 3 happen the game is up. Management killed it.

      That’s not agiles fault.

      • @[email protected]
        1•5 months ago

        But that’s what agile sounds like to management. They don’t understand the “it’s held together by hopes and dreams” communication, because all they see is something that appears to work. So why would they invest anything else in it.