Getting Software Done

17 October 2006

Part one of a two-part series on best practices for applying GTD® to software development is now available on both The David Allen Company web site and 43 Folders. I lay out software development and teamwork best practices we lived and breathed building GTD Connect. Hopefully a lot of the concepts extend beyond software development, into how to apply GTD to other long-range group projects. Part two is due out tomorrow. Enjoy!

Similar Articles:

  1. More Getting Software Done
  2. GTD® Connect
  3. David Allen’s TechGTD Panel

Liked this? Receive new ones in your inbox.

(You can unsubscribe any time.)

Posted in Articles, Productivity | Tagged , | Comments (2)

RSS Subscribe    Print Print   

  • http://ideamatt.blogspot.com/ Matthew Cornell

    Thanks for the article, Robert. Two points – First, it would be helpful to see how you think GTD compares with existing agile development approaches like XP. You referred a bit to it at http://www.robertpeake.com/archives/20-Extreme-Programming.html, but I think some detail would be helpful. Second, you may get a kick out of this article, which reverses the direction:

    Is GTD the “Extreme Programming” of Time Management?
    http://ideamatt.blogspot.com/2006/01/is-gtd-extreme-programming-of-time.html

    Cheers!

    matt

  • Robert

    Hey Matt, thanks for the link. I agree with a lot of what you said. As I mentioned in the TechGTD interview (which you as a Connect member have no doubt heard by now ;) ) I think just as GTD represents a kind of “advanced common sense” so does XP represent “best practices on steroids.” Both are distillations of what works into formal methodology. Check back tomorrow for part two of the article, which is all about GTD ala XP. Thanks for stopping by!