Probably just my misunderstanding of the entire methodology. Wikipedia has a better handle on it than I do:
http://en.wikipedia.org/wiki/Agile_software_development The principles expounded there seem sound (if more than slightly anti-bureaucratic). It may only be the proponents that I have encountered who either explain it or practice it badly. I've never actually been on a project that used it, so I should not castigate what I have not actually experienced. Mea culpa. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Friday, April 10, 2015 11:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: A New Performance Model In <985915eee6984740ae93f8495c624c6c2368d56...@jscpcwexmaa1.bsg.ad.adp.com>, on 04/10/2015 at 10:39 AM, "Farley, Peter x23353" <peter.far...@broadridge.com> said: >"Agile" may work in the fluid web world, I don't know what Agile specifies, but I was involved in rapid prototyping and we most definitly had reviews (code and design), unit testing and regression testing. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
