Comments on: GTD, an agile software dev process? http://troygilbert.com/2006/10/gtd-an-agile-software-dev-process/ Gamedev 2.0 Mon, 23 Apr 2012 13:14:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Uninstall Program http://troygilbert.com/2006/10/gtd-an-agile-software-dev-process/comment-page-1/#comment-23739 Uninstall Program Fri, 25 Jun 2010 10:06:41 +0000 http://troygilbert.com/2006/10/10/gtd-an-agile-software-dev-process/#comment-23739 Nice article:) Nice article:)

]]> By: Dan http://troygilbert.com/2006/10/gtd-an-agile-software-dev-process/comment-page-1/#comment-12314 Dan Mon, 08 Jun 2009 07:15:55 +0000 http://troygilbert.com/2006/10/10/gtd-an-agile-software-dev-process/#comment-12314 Great article. For implementing GTD you can use this web-based application: <a href="http://www.gtdagenda.com" rel="nofollow">http://www.Gtdagenda.com</a> You can use it to manage your goals, projects and tasks, set next actions and contexts, use checklists, schedules and a calendar. A mobile version is available too. Also there's an article on how the application can be used for software development. Great article.

For implementing GTD you can use this web-based application:

http://www.Gtdagenda.com

You can use it to manage your goals, projects and tasks, set next actions and contexts, use checklists, schedules and a calendar.
A mobile version is available too.

Also there’s an article on how the application can be used for software development.

]]> By: Troy Gilbert » More GTD for Software Dev http://troygilbert.com/2006/10/gtd-an-agile-software-dev-process/comment-page-1/#comment-303 Troy Gilbert » More GTD for Software Dev Wed, 18 Oct 2006 22:42:48 +0000 http://troygilbert.com/2006/10/10/gtd-an-agile-software-dev-process/#comment-303 [...] 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. [...] [...] 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. [...]

]]> By: Patrick http://troygilbert.com/2006/10/gtd-an-agile-software-dev-process/comment-page-1/#comment-298 Patrick Wed, 11 Oct 2006 19:39:10 +0000 http://troygilbert.com/2006/10/10/gtd-an-agile-software-dev-process/#comment-298 Sometimes I'm not sure what I should be doing, and start wondering if I've fucked myself by smoking so much reef ;) This is a nice methodology and I might incorporate some of them into my personal practice. Of course, cultivating an ideal corporate environment for game dev and R&D is another issue, but I suspect one that will be evident as a work-in-progress company, rather than in essays. Stay laid back! Sometimes I’m not sure what I should be doing, and start wondering if I’ve fucked myself by smoking so much reef ;)

This is a nice methodology and I might incorporate some of them into my personal practice. Of course, cultivating an ideal corporate environment for game dev and R&D is another issue, but I suspect one that will be evident as a work-in-progress company, rather than in essays.

Stay laid back!

]]>