Right Sizing Agile Development - MSDN Magazine Webinar

I logged into a web seminar this morning:

Title	Right Sizing Agile Development
Audience	MSDN Magazine subscribers and/or developers
Presenter	Steve McConnell is CEO and Chief Software Engineer at Construx Software where he writes books and articles, teaches classes, and oversees Construx’s software development practices. Steve is the author of Software Estimation: Demystifying the Black Art (2006), Code Complete (1993, 2004), Rapid Development (1996), Software Project Survival Guide (1998), and Professional Software Development (2004). His first two books won Software Development magazine's Jolt Excellence award for best programming books of their years. Steve has worked in the desktop software industry since 1984 and has expertise in rapid development methodologies, project estimation, software construction practices, and third-party contract management. In 1998, readers of Software Development magazine named Steve one of the three most influential people in the software industry along with Bill Gates and Linus Torvalds. Steve was Editor in Chief of IEEE Software magazine from 1998-2002. Steve is on the Panel of Experts that advises the Software Engineering Body of Knowledge (SWEBOK) project and was Chair of the IEEE Computer Society’s Professional Practices Committee. Steve earned a Bachelor’s degree from Whitman College and a Master’s degree in software engineering from Seattle University. Read more about Steve at www.stevemcconnell.com.
Brief	In this talk, Steve McConnell draws on Construx's extensive consulting work to dissect Agile development. McConnell names the Agile practices that have worked well for Construx's clients, describes the failure modes of Agile practices that have failed to live up to the hype, and explains how to right size Agile development for your organization.
Date/Time	Friday 17 April @ 7:00AM (NZT)
Slides	http://w.on24.com/r.htm?e=140117&s=1&k=1565037F2927EB78039F829A25208578
Impressions	I liked how he explained the differences between: Extreme Programming: lots of iterations of Analysis, Design, Build, Test (rinse and repeat several times) Agile Programming: few iterations of ADBT (staged deployments i.e. versioning) Waterfall Programming: no iterations (single monolithic)
Further Comments	I missed the first 10 minutes.