Drupal's modular nature can be a double-edged sword. With so much possible, part of the challenge is to stay focused on what is appropriate. What process will give your team the opportunity to make the best choices, stay on target, and deliver the best possible results? How do the different phases of Plan, Design, Develop, Verify, Train, and Support fit together? How much of each is just right? What are the critical components of each? Anyone considering a Drupal project in the future should find value in both the strategy and tactics covered.

UPDATE:
If you missed the presentation but would like to see something like it at Drupalcon DC, you can cast your vote at http://dc2009.drupalcon.org/session/drupal-process-management