You are in excellent company in the Drupal community. As you must be aware, there is no single approach towards tailoring software development engineering to Drupal.
If you'll go over past DrupalCon talks, slides and videos (as well as the Lullabot Do It With Drupal series) you'll find a lot to get excited about.
The site from DrupalCon Copenhagan is unfortunately offline now, but there was a gem of a gem there, which in my opinion is the first thing you should watch, and which is saved for posterity by
archive.com:
"Join Rob Purdie, ScrumMaster at the Economist, and Ezra Barnett Gildesgame, Developer at Growing Venture Solutions, as they discuss how the Economist uses Scrum to focus on completing work according to an exacting "definition of done."
We'll cover what "done" means in Scrum, and explain both the processes and tools we use to deliver thin vertical slices of functionality and coordinate with our development teams in London, New York, and Austin, Texas as we build the online product for a publication with a circulation of over 1 million in subscribers in over 200 countries."
So this is no abstract BS session, but really how they got things done, in terms of process in general and configuration management and testing in particular.
Grep in archive.com for drupalcon and you will find many more gems.
Topics you should find out about: aegir, drush, everything in code (and features), git, hudson and drupal, selenium and simple test and drupal...
Victor Kane
http://drupal.org/project/pft
On Wed, Jan 26, 2011 at 9:18 AM, mark bradley
<gopearls42@gmail.com> wrote:
Hello,
I'm new to Drupal, evaluating it for use in our corporate web site. I've looked through the documentation and I'm wondering if there's anything about how the traditional development flow of Development-to-QA-to-Production works with Drupal.
Thanks,
Mark
--
[ Drupal support list | http://lists.drupal.org/ ]