GTD Approach to Software Development

Robert Peake wrote a guest post on Merlin Mann's 43 Folders site.  He talks about the idea of creating software using the David Allen Company's GTD system.  (If you don't know what GTD is about, get the book and come back to this post.)  Here is an excerpt from the article:

Using a trusted system with the GTD methodology allows you to serialize your work life — to freeze dry it in a readable format (your system, be that a Hipster PDA, a plain text file, or a fancy graphical task manager). By effectively bookmarking your complete working state just enough so that you can pick back up where you left off, GTD actually allows you to deal with the boss that comes in every five minutes to get an update on your TPS report cover sheet. The promise of a trusted GTD system is the promise of never having to think twice about what you were doing; just as the promise of serializing data is that you don’t have to re-instantiate or re-calculate the structure you serialized. Store it, retrieve it, add water, and poof — you’re back up and running without any wasted cycles.

I am very interested in the tools that the team used to "bookmark" where they left off.  It is hard to do with most of the tools out there today.  It is painful to enter all the tasks that you need to complete easily in order to get them out of your head and be able to serialize where you were at.  This is one of the goals of Morale.  To be able to easily enter tasks, update them, and remove them freely as the software process and the things around it change.  I'm going to be looking more carefully at this GTD process for software development because I think it fits great with the tools that we are building.