7 ms·
If there is no way to tell, does it matter? It's easy to see the flaw in many failed implementations: they don't manage their schedules, they don't have succes
by chromatic 16y ago
If there is no way to tell, does it matter?
It's easy to see the flaw in many failed implementations: they don't manage their schedules, they don't have successful iterations, they don't manage their technical investments, and the only thing they don't do that agile suggests isn't usually worth doing is writing lots of specifications and documentation beforehand.
- narag 16y agoIt's easy to see the flaw in many failed implementations Is it also also easy to correct the flaw? I don't mean to blame Agile practices. It could be the case that Agile is a bad fit to some "corporate cultures" or certain project type and the result of someone pushing hard its adoption is to have some practices really used and other only in appearance. This could be what people hates. OK. that would not be "True Agile", but what difference makes for the poor guy that's forced to play a part? Edit: I've had Scrum in mind all the time when writting "Agile". Sorry.
- chromatic 16y agoIs it also also easy to correct the flaw? Not at all. If everyone involved in the project (everyone with a stake in the success of the project) agrees to give an agile process an honest chance, great. If not, you'll have trouble. A similar rule applies for coding standards, for test coverage, for security and logging, for transactional safety, for dieting, and for getting out of debt.