News for hackers. Stuff that matters.
Re:Coconut Headphones: Why Agile Has Failed (2014) by nine_k on Friday September 18, 2015 @01:11PM (#10240442)
In short: «The core problem is that non-technical managers of software projects will always fail, or at best be counter productive, whatever the methodology. Developing software is a deeply technical endeavour.» Technical excellence or at least competence is key and can't be replaced with any process. Estimates are not very useful; technical debt is dangerous toxic waste, and any process that does not treat it well is bound to fail.

A discussion 2 years ago: https://news.ycombinator.com/item?id=7389940

Re:Coconut Headphones: Why Agile Has Failed (2014) by capkutay on Friday September 18, 2015 @01:17PM (#10240493)
If that's the core message, why is the article titled 'Why Agile has failed'. Non-technical managers would ruin any engineering project whether it's agile or waterfall.
Re:Coconut Headphones: Why Agile Has Failed (2014) by hga on Friday September 18, 2015 @05:49PM (#10242260)
Because "Agile" (or at least some forms of it) claim to have solved this problem? Something I'm not aware of any other methodology (family) doing.