Am Donnerstag, den 19.06.2008, 12:58 -0400 schrieb Drew Jensen: > There is a lot of talk of the "Agile" approach to developing software. > One of the tenants of which is - build nothing beyond what you > absolutely must, add nothing that has not been explicitly asked for by > the 'customer'.
If used that way it is not the real thing but sort of misuse of the term agile development as an excuse for not fulfilling some expectations. What agile development does regarding the customer or targeted user is to evalutate the feedback from a release and adapt the requiremnts for going through the next iteration in design and implementation (and documentation btw.). > Report Builder may be a pretty good example - The development > organization or organizations decided in advance what those requirements > where and a roadmap was put up very early on for all to see. The actual > code has been releasing along the path put forth in that road map. I > suppose though one could also say that the Report Builder 'project plan' > came out of the feedback from the user base regarding the initial > release of Base and the report wizard. I don't think this has to do with agile development, too. If you have a fixed list of requirements this is exactly the opposite. An agile process includes adapting the list of requirements that will actually get implemented to the feedback coming from continuous integration giving the possibility for early releases done often. Respectfully, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
