Well, looks like even the man (or rather, The David) himself applies GTD to the software process (or more accurately, his CTO does). Here’s 43Folder’s two part series on the subject of “Getting Software Done” (part one) (part two).
While it’s not too much in the details (unfortunately), it does provide an interesting supporting point to my earlier post:
Another key with all of this, and a somewhat revolutionary approach, is that we don’t track bugs and feature requests in separate places. It all has to get done anyway. And because maintaining a comprehensive inventory of everything that needs to get done in one place, accessible by all the relevant people, we can very quickly re-calibrate to focus on what’s critical. Sometimes that’s a bug. Sometimes it’s a great new feature. Either way, we use the system to support us like a giant radar screen, and good communication in person, by phone, email, and IM to determine what’s critical and go after it.