Having missed the session at Revolution (I was on the way to my plane), I have just gotten connected with this board. I guess things have been moving slowly ...
I'd like to throw out a couple of thoughts based on going through the slides.
One is that few of us are in the position of dealing with well-documented systems that have been under good ALM practices for their entire life cycle. Even if we have our own code ... and many of us are dealing with someone else's code ... and have implemented some ALM practices, chances are that a lot of the life of the application was under more "cowboy" management practices and many applications are still pretty far in that direction. That being the case, one of the important ingredients in the application life cycle is analysis ... figuring out what is there already in order to know where and how to make any changes. There was a slide of analysis tools in the deck, but there are many more than were listed there. As a starter, I refer you to my PUG Challenge EMEA session http://cintegrity.com/content/Analysis-Existing-ABL-Code . In particular, I would point to Joanju Analyst and ABL2UML as particularly sophisticated tools which help the process of understanding one's application.
Another is that there is no mention in the deck of modeling. I know that modeling hasn't been an especially popular approach in a lot of ABL history, but I think it is an increasingly important tool to consider. Modeling of an existing application provides a foundation for analysis and planning of application evolution which dwarfs other approaches. Modeling as a part of the analysis and design for a new application or new application components provides the potential for substantial reductions in development effort, not the least of which is from doing the right thing the first time instead of iterating toward a solution. And model-based development offers the possibility of improvements in both productivity and quality which is exactly what one needs to build responsive applications. See http://cintegrity.com/content/Model-Based-Development-Day-Life for a taste and http://cintegrity.com/content/Rapid-Business-Change-and-ABL-Productivity and http://cintegrity.com/content/Path-Model-Code-Translation-ABL for some background.
As for Agile development, see the attached whitepaper at http://cintegrity.com/Lahman for a discussion of why model-based development, far from being an expression of old waterfall development models, actually enables the Ultimate Agile.