tag:blogger.com,1999:blog-3233976179816390421.post512504846329452881..comments2023-04-29T16:11:52.799+02:00Comments on Axel's Corporate IT Corner: Agile's Prerequisites, Risks, Limitations and WeaknessesAxelhttp://www.blogger.com/profile/07192902657903655063noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3233976179816390421.post-87148086386529969582013-08-03T15:27:38.351+02:002013-08-03T15:27:38.351+02:00A very good account on what Agile is and means for...A very good account on what Agile is and means for the organisation. <br /><br />As you are pointing out, Agile leads to minimum solutions, often modelled directly after the customer's wishes - so if the client doesn't know much about what should be delivered (for instance when it is a new application area), the project could end up producing a useless "solution" (which is then the wrong name, as it should then have been a solution to something, meaning: useful).<br /><br />You do mention the client's availability is a prerequisite. I believe that this can easily become a severe issue - short sprints of development, adjusted after the client's feedback, really need this feedback, so if the client doesn't have time or will to get engaged in this and stay engaged throughout the project, it will lead to trouble.<br /><br />So Agile definitely isn't for every client and every project, I fully agree on that.Jørgen Wintherhttp://nocrisis.netnoreply@blogger.com