Brian Gupta wrote: >> > In agile development, you begin with a list of simple requirements >> > without a detailed description of how you are going to get there. You >> > then rush straight to implementation. After implementation, you pass >> > back to customer for feedback at the soonest possible instance. You >> > then rush again for a period of time, (say 2 weeks) and kick out what >> > you have to the customer. Keep repeating indefinitely. >> > >> I think you have a slightly warped view of Agile development! As an >> Agile evangelist, I hate seeing words like "rush straight to >> implementation" and "kick out what you have to the customer". Done >> correctly, Agile processes are a very structured and customer focussed. > > I chose to use words that are deliberately provocative, and engender > some of the fears of agile methodology. Agile methods do emphasize > real time communication, over written documents. Agile methods also > emphasize "working software" as the measure of progress, and produce > very little written documentation relative to other methods. In reality, they tend to produce a lot more and more accurate documentation than "traditional" methods, working live documentation called unit and acceptance tests! > This has > resulted in criticism of agile methods as being undisciplined, which > BTW is the point I was trying to emphasis with my choice of words. > Ah.
Ian. _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
