3 ms·
If you argue agile isn't working, you must have some hypothesis of both what it is and what it would look like if it worked. I fail to see that in this article.
by alkonaut 9y ago
If you argue agile isn't working, you must have some hypothesis of both what it is and what it would look like if it worked. I fail to see that in this article.
There is also the other problem with complaining agile dosn't work - it's that there are no clear candidates for what does work.
To me, agile is mostly about measurement. If you have a process that is exactly as slow as what you did before you "went agile" but now you KNOW how slow you are, and you have realistic deadlines, know beforehand when you will miss them and so on - then agile mostly works for you.
- tempodox 9y agoPlus, the author gives zero sources for the statements and numbers they present. We just kind of have to believe them - or not.
- pdimitar 9y agoThis is not a PhD thesis, so your comment is meaningless. It's an opinion / rant. What sources would you accept? Additionally: don't believe him, what's the problem with that. Just don't.
- SAI_Peregrinus 9y agoThe main issue is you can pick at most one of three from "good", "cheap", or "fast". Agile gets you there fast, but the product is crap. Traditional engineering design results in good reliable products, but typically won't be either fast or cheap. Outsourcing everything to developing nations gets you cheap crap long after you needed it. I prefer traditional engineering design, but I prefer to work with hardware so there's no real ability to patch.