Drupal implementation methodology

Hi,

I've been implementing mostly commercial CMS tools in mid-size organisations (5 to 150 employees) for the past 6 or 7 years. In the last 2 years I did quite a few Drupal sites. I'm always involved in these projects as a functional analysist and project manager, not as a developer.

I'd like to develop a light methodology for implementing Drupal projects. I see this as a document, a number of checklists, and maybe a set of PowerPoint presentations to support the implementation process from pre-sales demo, to quote, to kickoff meeting, to analysis, to implementation, testing, presentation, training, going live, debriefing, and ongoing support.

I found one interesting post here: http://www.drupal.org.uk/node/153. I noticed that I currently use a similar approach in projects, starting with a "prototype" which is a default Drupal install, some stable modules, and some configuration.

I've also been reading about the Getting Real approach: http://gettingreal.37signals.com/. Some of these ideas might be usefull too. Yet, Getting Real seems to be quite focussed on custom development, maybe an open source CMS implementation needs its own approach.

So here are my questions:
* anyone using a special methodology or approach when implementing Drupal sites?
* is it usefull to create a book-node about this an collect all available information?

Thanks !