tag:blogger.com,1999:blog-31006871.post5470845002321193542..comments2007-07-18T09:10:17.383+02:00Duncan Drennanhttp://www.blogger.com/profile/18356141566912975917noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-31006871.post-86542245144673415612007-07-08T15:39:00.000+02:002007-07-08T15:39:00.000+02:002007-07-08T15:39:00.000+02:00As it applies to software engineering at least, the <A HREF="http://agilemanifesto.org/" REL="nofollow">Agile</A> camp says many of the same things. <BR/>They advocate low-ceremony, high-discipline processes that minimize many of the bad things more "formal", paper heavy processes do. At the same time they maintain measurability and transparency. <BR/>For specific instantiations, look at <A HREF="http://en.wikipedia.org/wiki/Scrum_(development)" REL="nofollow">SCRUM</A> and <A HREF="http://en.wikipedia.org/wiki/Extreme_Programming" REL="nofollow">Extreme Programming</A>.<BR/>I recently read a McKinsey Qaurterly article (free registration) (and a <A HREF="http://www.edmblog.com/weblog/2007/05/lean_applicatio.html" REL="nofollow">blog with some nice comments</A>) about applying Lean Manufacturing principles to software, which boils down to the same things.<BR/><BR/>I agree it's very important to apply appropriate process and monitor it carefully.Alberthttp://www.blogger.com/profile/04042000915768538262noreply@blogger.com