not much new in these mendioms.
traditional waterfall methods are one way to build apps and in some cases are a very good way to build apps - as long as one can go back up the waterfall.

Can any process be completely waterfall or completely agile? I think blending these methods and taking changes case by case is the most sensible option. Get a bunch of people who "get it", are committed, and work as a team, and you can do anything.

Connie,
I completely agree. Both methods have their strong points, but one is gaining in popularity and one is losing, for the reasons outlined in the Mendioms. It's often easier to say whether or not a project was truly 'agile' or not once it is completed. On the other hand, going into a project with a team that is committed to an iterative process, is rarely thought of as a waterfall guided team. It takes a true 'agilist' to say 'this will be, this is, this was - an agile project.' - But if you start your project with this mindset, you'll see a much more liberated and productive team.

I love these slides! They are so true.