{ "href": "/post/2009/10/26/agile-gone-bad/", "relId": "2009/10/26/agile-gone-bad", "title": "Agile Gone Bad?", "author": "pmjones", "markup": "html", "tags": [ { "href": "/tag/php/", "relId": "php", "title": "PHP", "author": null, "created": null, "updated": [], "markup": "markdown" }, { "href": "/tag/programming/", "relId": "programming", "title": "Programming", "author": null, "created": null, "updated": [], "markup": "markdown" } ], "created": "2009-10-27 02:19:22 UTC", "updated": [ "2009-10-27 02:19:22 UTC" ], "html": "
\n

Agile ain\u00e2\u0080\u0099t agile no more when adopted as the official enterprise software development process. The problem with agile is \u00e2\u0080\u009cagile != flexible\u00e2\u0080\u009d.

\n

Agile was born in the world of contractors who have to show something for the money at every status meeting. For a while clients let themselves fooled with use cases written on many hundreds of pages but this doesn\u00e2\u0080\u0099t work no more. They smartened up and demanded to see something working, for a change. Agile came in handy because it allows to show a prototype early on. As long as you keep adding features to it and you are able to demo them there is a good chance your contract will be extended.

\n

While in theory the Agile methodologies tell you to be flexible, the cruel reality is that most people that apply them don\u00e2\u0080\u0099t think a lot before taking the manual and enforcing every bullet point with a thick stick.

\n
\n

via Software development dogmata - good practices gone bad | Little Tutorials.

\n" }