Why Isn’t Agile Working?
Couldn&#x27;t disagree more with this article, is this even written by a programmer? Agile takes into account the very real &#x27;semantic cost&#x27; when translating from user requirements to actual code.<p>Code is so specific and brittle compared to the lovely fuzzy English language that we think and write in, that we can never get the requirements just right. The biggest problem is integration of ideas into an existing system. Yeah ok you want to extend the login screen to support one extra field? That&#x27;s great but after a couple of days work, it turns out that 2 years ago Joe Bloggs added some complex verification algorithm no one understands to a stored procedure, oh which contains about 30 other input fields, and so is going to take an extra week to untangle. The procedure is also used in 20 other places too and there&#x27;s no unit tests covering any of the functionality.<p>Agile gives the programmer a voice in the process, and once they update the tasks and time estimates, the feature&#x27;s priority can be re-evaluated. Treating development as a one shot process is just doomed to fail and more stressful for everyone involved.