I'm a sysadmin and my workflow seems similar to yours.
In GQueues, I create a Parent task for the project which contains a title, brief summary and possibly a link to the email or ticket which started off the project in the first place. If this subtask requires additional, signifigant steps; I add these steps as sub-subtasks. I end up with a nice, organized hierarchy showing me the significant tasks required to complete the project. I believe this is similar to the method used by
James, Russ & Dane (and you?); and this fits into the GTD/ZTD philosophy that "you don't actually do a project; you can only do action steps related to it."
The problem with this method is that the 'next
actions' Smart Queue only shows me the Project parent task, not the subtasks
required to complete that project. I believe that some of this problem is due to GQueue's GTD system being built around tags, while many of us actually organize using Categories, Queues, Tasks and subtasks.
Have you managed to get the Next Actions smart queue working with your Project queue?