3 ms·
I've seen Agile be hugely effective when actually done. It results in a much better product that's also more suited to what the customer needs, and therefore mu
by lmm 6y ago
I've seen Agile be hugely effective when actually done. It results in a much better product that's also more suited to what the customer needs, and therefore much more fulfilling to work on. It cuts through many of the most frustrating and wasteful parts of other kinds of software development at a stroke (e.g. endless architectural arguments). I genuinely think it's the best thing that's happened to my career. So it's frustrating to hear people attack it and especially frustrating when it gets attacked for the opposite of what it actually is.
I don't know how to make people stop lying about what they're actually doing (I wish I did), but I don't think it's reasonable to expect any kind of process to work when you do the opposite of what that process actually tells you to do. (And I'm quite prepared to entertain the possibility that an organisation that actually committed to following RUP or Six Sigma or whatever and followed through on it might be better than half-assed non-Agile "Agile". But I haven't found the HN-endorsed "lol no process" to be effective in practice either)