I'm new to the forums but did scan to see if this type of question had already been asked. Please forgive me (and provide a link!) if I'm going over old ground!
I've been using GTD for a few years and am a big fan of the system, it really works for me.
Professionally I work in the software industry, and we run projects lasting 9-18 months with teams of 5-10 software engineers. The company does not use or advocate GTD.
In terms of goals/responsibilities/personal projects/next actions I do fine with GTD.
In terms of team leadership activities (review staff, write proposals, produce presentations etc) I do fine with GTD.
However the projects my team work on will have hundreds or thousands of "work items" and "bugs to fix" in a database, with project planning done statistically by people outside of my team, including gant charts and other planning tools. Some of these work items will be assigned to me, some I am waiting for, and a lot I don't care about.
As it's database driven, I can call up a list of items assigned to me easily, but there the similarity with GTD stops. There's not a "waiting for" list analogy in the system. Separate features of the software have their own work items within each software project, but even these can be man-months of work and a great many items.
I'm looking for a way to co-exist the two systems. How on earth do I reconcile these "super projects" with the GTD system?
There is inevitably more to do than I will ever have time for, so making contextual and priority choices about what to do right now is difficult for me.
Really I'm looking for feedback from others who manage large long-term projects and the like. I can get by as I am, but I can always learn some new tricks!