Slashdot Mirror


What Does Everyone Use For Task/Project Tracking?

JerBear0 writes "I work as the sole IT employee at a company of about 50 people. I handle programming, support, pretty much anything that is IT related, or even that plugs in. As seems to be true with many small companies, the priorities seem to shift quite frequently. As a result, I've always got multiple programming (both new systems and improvements/changes to existing systems), integration, research, maintenance tasks/projects on my To Do list, in varying stages of completion. At any given time, I need to be able to jump back to one of these items and pick up where I left off. I am currently using Outlook Tasks, and then end up referencing my notebook and email for those dates to figure out exactly where I left off. It works, but not well. If it's been a while, I'll end up losing an hour or two just tracking everything down. I looked at using MS Project / OpenProj, but they want an individual file for each project, and I want at least the project/task list all on one screen. Essentially what I'd want would be a Task List on steroids, allowing for hierarchical subtasks, attachments, and prioritization. Ideally it would be a desktop app, but a locally-hostable web app would be okay. In some of these projects I may want to include proprietary information, which I really don't want floating out in the cloud outside of my control. I know I'm not alone in this problem, so what do you guys (gals) use to address this?"

50 of 428 comments (clear)

  1. redmine by semargofni · · Score: 5, Informative

    I use redmine, see http://www.redmine.org/

    1. Re:redmine by Cryacin · · Score: 3, Interesting

      I use BSmart from Bijingo. www.bijingo.com Pretty slick and it does pretty much what you want.

      --
      Science advances one funeral at a time- Max Planck
    2. Re:redmine by the_g_cat · · Score: 2, Informative

      Second that, although I use it in combination to Things (by CulturedCode) on Mac/iPhone.

    3. Re:redmine by bluec · · Score: 4, Informative

      Redmine is the correct answer. Can't believe parent isn't modded up more. We use it for all web/software development projects because of its excellent trackers and repository integration. We are just about to roll it out across the organisation for all types of projects and management tasks. It is extremely flexible and different types of projects can have different features - wiki, forum, file sharing, bug/request tracking, time tracking, gantt charts, code repos, the whole shebang. Loads of addons too and very stable. It is a bit like basecamp, but better, and free/libre.

    4. Re:redmine by INT_QRK · · Score: 2

      I use OMNIPLAN on my MAC. Very good interoperability with MS Project.

    5. Re:redmine by turbidostato · · Score: 3, Informative

      "I use redmine, see http://www.redmine.org/"

      I'd say, yes... but not.

      Look at the environment:

      "I work as the sole IT employee [...] I've always got multiple programming (both new systems and improvements/changes to existing systems), integration, research, maintenance tasks/projects on my To Do list, in varying stages of completion. At any given time, I need to be able to jump back to one of these items and pick up where I left off"

      So:
      1) His best tool must be his mind: he must use it to set his own procedures (and exceptions), so pointing to reads like David Allen's "Getting Things Done" or "Limoncelli's Time Management for System Administrators" are a foremost.
      2) Given the right ideas are in his mind and given that it's a solo show, the leaner the tools the better: he don't need contrains on the tools when he can adopt them by his own criteria. That's where even such a fine tool like Redmine is a bit of an overkill. I'd find in this case its conceptual father to be a better fit. Trac, that is.

      Let's have a look about how Trac fits the bill:
        * For a start it really helps the guy that do the thing instead of getting in his way in favor of the one that plans the thing (so, i.e. there are not -at least by default, fixed workflows nor fancy flowcharts to the content of a project manager but absolutly unuseful for a single or a short development/multitasking group).
        * It allows (but not commands) tight but lean integration between wiki pages, tickets, milestones and source code management. You will fastly and easily group your tickets by milestones (like, say, "work as usual year 2009" or "summer campaign"), by components (like "central servers", "help desk"...), by type (like "bug", "enhancement"...), by priority and severity but you will be *not* forced to use them if you don't want to (as an example, shorter shops tend to use either priority or severity, but not both).
        * It lacks "proper" multiproject and nested tickets support but, as I already said, that's not a problem since you are alone and workflow/procedures are basically in your head (and described on a wiki page too). In example, a component/milestone combo provides for a nice solution for your short, unbudgeted, as time allows, personal/internal "microprojects", and being wiki-based, hierarchycal tickets can be easily mimicked using a "superticket" ticket type that links to all the related "subtickets" which in turn "backlink" to the parent.

      So, my recomendation is Edgewall's Trac because of it leaness and functionality, more or less like this:
        * Wiki pages organized by "machines", "services" and "procedures" with proper links among them (a procedure affects some services that are offered by some machines; a machine hosts some services -or parts of them; each service has some associated procedures and expands through one/some machines).
        * Bug/Enhancement tickets for "usual" day-to-day activities eventually grouped by milestones (like "operations 2009") and components (like "core services", "helpdesk", "CRM"...). They allow for a description and a variable number of notes either direct or question/reply style, so you will know exactly where did you gave it six months ago, when you last time worked on it; its wiki syntax will allow for links to the pages for the affected machines/services/procedures and even the exact transaction on the source management system where/when you activated that new service or corrected that bug.
        * Project-like components/milestones/tickets for bigger tasks (aka "microprojects").
        * ...and your own intelligence and discipline to firmly tie everything in place.

    6. Re:redmine by SirKveldulv · · Score: 2, Informative

      If you want to use redmine (or some of the other software mentioned below) on windows, bitnami have a stand-alone package for this. Just run the setup.exe and you'll be live in 5 minutes.

      Redmine
      http://bitnami.org/stack/redmine

      Trac (issue tracker)
      http://bitnami.org/stack/trac

      Tracks (gtd app with a familiar sounding name)
      http://bitnami.org/stack/tracks

    7. Re:redmine by tolan-b · · Score: 2, Insightful

      If you're using Eclipse for development then combining Redmine (or one of the many other supported bug trackers) with Mylyn (using http://sourceforge.net/projects/redmin-mylyncon/develop ) can be a big win. More so if you have multiple developers but still. Among other things Mylyn stores a context against your bugs (locally by default but it can attach it to the ticket for other users to fetch). The context keeps a track of which files you were working on, including which functions if you're using the Java tools, and restores them when you activate the task/ticket.

      Also they have a commercial add-on called Tasktop which extends the integration out to other more desktop oriented stuff like Outlook and Firefox.

  2. Bugzilla and Wiki by sky289hawk1 · · Score: 4, Interesting

    A combination of Bugzilla and Wiki. Wiki keeps track of backlog. Bugzilla keeps track of tasks.

    1. Re:Bugzilla and Wiki by grcumb · · Score: 5, Informative

      A combination of Bugzilla and Wiki. Wiki keeps track of backlog. Bugzilla keeps track of tasks.

      If you're going down this road, then just install and configure Request Tracker. It's got great workflow management, uses email (which works for all but network-related tasks) as the primary interface and has some great reporting tools, so at the end of every month you can hand your boss a shiny little report showing just how productive you are.

      For bonus points, it also stores the history of every request, so if you need to, you can also demonstrate to your boss what a prick Henderson in HR is, and that you cut off his Internet access because he didn't seem to be able to stay away from Furry sites during working hours.

      Okay, seriously: RT is well-designed, well-documented and well-supported. It's got a lot of solid add-ons (which might or might not have significance for a 1 man IT dept.), and though it takes a little effort to grasp, it's remarkably rewarding in terms of simplifying your day.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    2. Re:Bugzilla and Wiki by eulernet · · Score: 3, Interesting

      At my work, we used Bugzilla extensively, but it was because one of our developers maintained it, by coding some new components.
      It is really oriented towards bug tracking, but it's not very well integrated with anything else.
      For example, how can you automatically link a wiki page to a bug, when you do a commit on a SVN server, then run a build ?
      It's also a mess to maintain, since it's written in Perl.

      We recently switched to Trac because we needed a more complete integration between the automated build process, the wiki, the bug tracking and the frequent releases (we try to work with agile methodologies).

      Frankly, Trac is not very good on each of the above points, but it's easy to use, fast and light and it's written in Python (and our Bugzilla maintainer is a Python expert, so he's much happier).
      Bugzilla is slow and if Mozilla did not put resources on maintaining it, it would have died since a long time.

      Note that using two different tools (Wiki and Bugzilla) leads to developers concentrating on Bugzilla, and never updating the wiki.
      On the contrary, having the wiki and bug tracking forces them to update the wiki.

    3. Re:Bugzilla and Wiki by RichardJenkins · · Score: 2, Interesting

      We use this, except we have a subversion hook which forces commits to be associated with bugs, and adds a link to the commit in viewvc as a comment in the bug. Seems to work pretty well for small teams on multiple small projects.

    4. Re:Bugzilla and Wiki by tbischel · · Score: 3, Interesting

      I've found Fossil extremely easy to use as an individual programmer... it incorporates wiki, issue tracking, and version control through a simple interface, the server software is a single executable and runs on the client with no setup required, and it is free. When you begin working in larger teams, the model is distributed version control. Its pretty slick.

    5. Re:Bugzilla and Wiki by rtfa-troll · · Score: 5, Interesting

      What's the advantage of using the proprietary options over Trac? Especially since that can run on top of an advanced VCS like GIT, I think it's pretty close to ideal.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    6. Re:Bugzilla and Wiki by rtfa-troll · · Score: 3, Informative
      Err.. Edgewall, the people who write it also provide commercial support for trac. Note: I haven't tried it yet myself so this isn't an endorsement, but normally Free software support is much better than proprietary, especially since you have the option to find another commercial option if you are unhappy.

      So what was the benefit again?

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    7. Re:Bugzilla and Wiki by kobaz · · Score: 3, Insightful

      It's also a mess to maintain, since it's written in Perl.

      Nice troll!

      "I hate X because I can't use it properly". "I hate X because other people can't use it properly".

      It's a pretty common misconception that a *language* makes things hard to maintain. I've seen horrible C code, I've seen excellent C code. I've seen horrible PHP code, and I've seen excellent PHP code. And of course I've seen some amazing Perl. It's a matter of development experience combined with time and effort of the authors, that makes a project is easy to maintain or not... not the language.

      If your bugzilla guy is a Python expert, then maybe his skills are lacking in Perl... which is why it's hard to maintain... just a thought.

      --

      The goal of computer science is to build something that will last at least until we've finished building it.
    8. Re:Bugzilla and Wiki by kobaz · · Score: 3, Funny

      I simply said that Bugzilla has been written since a long time, it's pretty old and over-bloated, and hard to maintain.

      Heh... no, you didn't say that. You said:

      It's also a mess to maintain, since it's written in Perl.

      --

      The goal of computer science is to build something that will last at least until we've finished building it.
  3. Clocking It by sheetzam · · Score: 4, Interesting

    http://www.clockingit.com/ Might be worth a look. Keeps track of stuff you need to do, and will let you keep track of time spent doing it as well. Definitely a help if you're looking to prove you need help some day. And yes, you can install a copy of it on a local server.
    Heck, might be a good tool for others in your office, for that matter - this isn't a problem you're alone in having in your company.

    --
    "Actually, I enjoyed this in the same vague, horrible way I enjoyed the A-Team" P. Opus
  4. Re:what we use by jo42 · · Score: 5, Funny

    We've upgraded to soft clay tablets and pointy sticks from hand painting on cave walls. There was a great debate on the merits of the permanence of the new technology until Ugh pointed out that the clay tablets harden if you leave them on the fire and that you can also take them with you when moving to the summer caves.

  5. Something WebBased by nahdude812 · · Score: 3, Informative

    I used to use Mantis and create tickets for different tasks.

    I have switched to OpenGoo, this is a slick easy to use web based lightweight project management software. It can be used to give visibility to others in the organization regarding what you're working on if you so choose.

  6. TikiWiki by dikdik · · Score: 2, Interesting
    I set up TikiWiki for my department to track projects. We are a commercial HVAC firm (my dept is the automation side), so CVS and the like don't (at least I don't think!) really apply. But I do the engineering and layout, with others doing the actual installations and we needed a way to easily transfer information. They always have their laptops with them, and have VPN access to the office, so this idea came to mind.

    It has worked pretty well, and quite a few people in other departments have started using it too. It's a nice way to do "brain dumps" and record those things people tend to say in passing in the hall! I still have a few people that "forget" about it and call / barge into my office to ask a question. "Did you check the wiki?" standard response now!

  7. Nice big by i.r.id10t · · Score: 4, Interesting

    Nice big whiteboard w/ several color markers. Grid it out into colums/rows if needed using blue painters masking tape.

    --
    Don't blame me, I voted for Kodos
    1. Re:Nice big by NeutronCowboy · · Score: 3, Informative

      Indeed. Not to mention that if someone comes by and asks "Why isn't this done yet?", you can point at the 20 tasks ahead of his and ask him which one ought to be re-scheduled in his favor. It drives home quite nicely that you aren't just waiting for people to grace you with requests for work.

      Alternatively, I've found TiddlyWiki immensely useful - it's lightweight, allows for cross-linking and makes searching for those meeting notes a cinch.

      --
      Those who can, do. Those who can't, sue.
  8. WebCollab by MooMooFarm · · Score: 4, Interesting

    I use WebCollab, great tool and fits the description of a "task list on steroids" and its open source! What is nice about WebCollab is that you have one object, a task, and a task can have multiple tasks in a hierarchical organization or can be by itself. http://webcollab.sourceforge.net/

  9. I use an Excel spreadsheet by gestalt_n_pepper · · Score: 4, Funny

    But I always wash my hands afterwards.

    --
    Please do not read this sig. Thank you.
  10. Omnifocus! by klagg · · Score: 2, Insightful

    Works fantastically well, but for Mac only. So chances are it won't work for you. It does everything you ask for anyway.

    --
    Free GPL Java Mobile Tetris game: Jamos
    1. Re:Omnifocus! by ogdenk · · Score: 2, Insightful

      Even better for project management: OmniPlan

      The Omni group has some great stuff.

    2. Re:Omnifocus! by Lord+Satri · · Score: 3, Informative

      I must agree. After a few months with OmniFocus, it really does help me reduce stress and stay focused (well, more focused anyway ;-).

      I wrote a personal review last summer: Getting Things Done App Reviews: OmniFocus, Things, Life Balance, ThinkingRock and Chandler (no ads link). Chandler being open source.

  11. redmine, launchpad, basecamp by kikito · · Score: 3, Interesting

    I use redmine, which is opensource, and free as long as you have a server for it.

    If I liked bazaar, I would use launchpad.

    If I wanted a payed, supported option, I'd go for Basecamp.

  12. Task Coach by northrange · · Score: 2, Interesting

    I use Task Coach It has hierarchical subtasks, attachments, and prioritization. I really like the ability to create tasks automatically from emails.

  13. Go oldschool by Keruo · · Score: 3, Interesting

    I work in almost identical setup and simply use two notebooks. In notebook one I keep generic todo list, which travels with me. Second notebook sits on my desk. I keep more per project detailed data on it describing how I did something or just basic notes when trying to solve something. If the project is bigger, there will be separate binder for it additionally.

    The generic notebook gets decoded into excel file which has sheet for each month, so I can track what I've been doing past year(s). Also it helps when troubleshooting reoccurring problems.

    --
    There are no atheists when recovering from tape backup.
    1. Re:Go oldschool by nine-times · · Score: 4, Interesting

      I agree with keeping it old-school-- or at least it's good to avoid making things more complicated and technological than they need to be.

      If you're trying to do something very complex and specific, there are probably good tools out there for you. Other people here are talking about tools that manage trouble tickets and stuff, and if you need that, great. Try some out, see what works. However, don't undervalue the old pen and paper. If you're going to use a computer, don't be afraid to type some lines into a text editor and save the text file, relying on simple directory structures and file names to keep things organized. As a techie, it may disappoint you to resort to such simple approaches, but the simple things still work.

      I may be stating the obvious that everyone here already knows, but you might want to read Getting Things Done if you haven't already. The GTD fad may be overblown, but there's some good advise in there for making task lists.

      But generally, my advice would be to not even try to devise a technical solution that will "keep you organized". Either you're organized or you aren't. If you add a complex technical solution on top of your disorganization, you'll probably end up dealing with your technical solution in a disorganized manner and it won't work. Get organized, then figure out a system that will help you skip over some of the more tedious steps of your workflow. Also, don't try to put all your information into a single task list. Keep the task list simple enough that you can glance at it and see if there's anything you can check off. If you need more information on a given task, keep a resource file somewhere else and store all the details there.

      But regardless of this advice, you have to find a system that works for you. There's no "proper" way of handling these things that will work perfectly for everyone.

  14. Emacs org-mode by Enfors · · Score: 4, Insightful

    Are you an emacs user? If so, then I definitely recommend org-mode: http://orgmode.org/

    It's notes mixed with todos on steroids (which themselves are on steroids). There's nothing it can't do. Check it out.

    There's a Google tech video about it here: http://www.youtube.com/watch?v=oJTwQvgfgMM

    --
    -Enfors-
    1. Re:Emacs org-mode by flynt · · Score: 2, Interesting

      I second org-mode. Basic emacs is worth learning just so you can use it, honestly.

    2. Re:Emacs org-mode by Saint+Aardvark · · Score: 2, Interesting

      Another vote for org-mode. Checklists + todo + export-to-whatever makes awesome.

    3. Re:Emacs org-mode by Jason+Earl · · Score: 2, Interesting

      Even if you are not an emacs user org-mode is awesome.

  15. Trac works well by talcite · · Score: 2, Interesting

    I've worked with people in the same situation (small office & 1 person IT team) before.

    They used Trac (http://trac.edgewall.org/) to keep things organized. It works really well because it has integration with the standard SVN features for software development, while tickets/milestones can be used for non-programming projects. It even scales well with job assignments if you eventually get an IT team.

  16. Microsoft OneNote by FaxeTheCat · · Score: 2, Informative

    Although not strictly for tracking projects, I recently started using Microsoft OneNote.
    I find it really great for keeping lots of notes in a semi structured way. I used to have a lot of files and pieces of paper with notes. Now I have it all in a OneNote file.
    It also integrates with other MS products, so you can create an Outlook task directly from some note in onenote.
    Don't take my word for it. You can most likely download a time limited trial from Microsoft and check it out, or watch the demos available.

    Of course it is from Microsoft and it costs money, but if you can get over those hurdles, it is a good product.

    ...and if there are similar things out there, let us know. It is not the specific product that is the important, but the functionality.

  17. Retrospectiva by k33l0r · · Score: 2, Interesting

    You might want to have a look at Retrospectiva. It has ticketing, milestones/goals, code reviews, a wiki add-on, a blog add-on, and an Agile project management add-on. Plus you're free to develop your own add-ons. It's fully open source too...

  18. Use a proper issue tracking system by dirkdodgers · · Score: 2, Informative

    http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems

    You and your customers create issues describing what they want done. You estimate them. They prioritize them in the order they want them done. You track your time and status on each issue. You can add notes and artifacts to each issue so that you can pickup where you left off if priorities change.

    This might sound like a lot of extra work. Not only is it not a lot of work, it is hugely to your advantage in two ways:
    1. When the time comes, and it will, that whoever pays your bills wants you to justify your existence or justify why tasks are taking longer than they want, you can point them to this system and show exactly what you've done, where your time has went, and when priorities and requirements have changed.

    2. When you're ready to move onto a larger company, having personally been responsible for rolling out and implementing an issue tracking system is a nice accomplishment to put on your resume.

  19. Lucy in the Sky with Diamonds, dude. by GPLDAN · · Score: 2, Funny

    Here's a novel approach:

    Take massive quantities of LSD, combined with strobe light therapy, aka MK Ultra stuff - until you develop Dissociative Identify Disorder aka Sybil Effect and then assign each one of your personalities a non-competing task. Note: you may have to go Memento on this, and write the tasks on your body for the next personality to see.

    What you should find is that you cycle personalities often enough to load balance the work properly. Take Thorzine as needed to adjust timing.

    I think you will find that.... errerggshdgs... wait, what? Ignore that advice!

  20. Trac = Bugzilla and Wiki by rysiek · · Score: 5, Interesting

    Trac is a Bugzilla, Wiki, and then some - plus it has thousands of plugins. Also easy to administer and manage. Great tool, I use it for many projects.

  21. Re:what we use by Evil+Shabazz · · Score: 4, Funny

    I think it's been fairly well established that African swallows are no better at carrying coconuts. It's a question of mass ratios. That said, there have been recent discoveries in OCT protocols (octopus coconut transport) that you may be interested in.

    --
    Down with the career politician! SUPPORT TERM LIMITS
  22. Re:what we use by Utoxin · · Score: 2, Funny

    What do you do to stop the octopi from stealing the coconuts to live in?

    --
    Matthew Walker
    http://www.tweeterdiet.com/ - My Diet Tracking Tool
  23. TaskFreak! definitely. by burnin1965 · · Score: 2, Informative

    TaskFreak!

    - project/task list all on one screen CHECK
    - a Task List on steroids CHECK
    - hierarchical subtasks (not 100% sure on this feature in TaskFreak!)
    - attachments CHECK
    - prioritization CHECK
    - a locally-hostable web app CHECK

    Not sure how secure TaskFreak! is for public internet access but it is multi-user with passwords and permissions.

  24. MS Onenote by fast+turtle · · Score: 2, Informative

    Big Question: Why aren't you using the Outlook Journal to at least track projects? It can link all of the information (messages, tasks and files) into a single location. Very handy and you've already got it.

      Another option that will work nicely is Onenote by MS. It's now part of Office and expands on the Outlook Journal capabilities. It uses tabs to keep things organized, you can add pages as needed, link in other documents such as research information, web links and maybe track emails like the Outlook Journal. It also has a shared notebook feature that's for networks and the best thing is, you might be able to convince the boss to get a copy since it's fairly cheap from your normal office super store. I've only been using it for 6 weeks now and it's already become the must have tool for me. Can't say how well it'll work for you but worth giving it a try

    --
    Mod me up/Mod me down: I wont frown as I've no crown
  25. Salvation is in the method (GTD) by tamnir · · Score: 4, Informative

    There was a similar comment posted, but it lacked explanations and has not been modded up yet, so let me go into more details.

    Your current task management solution does not work so well, and you are looking for a tool that, you hope, will automagically make everything work for you. Let me tell you from experience: this won't happen. You may get a small boost at first, when using a new shinny "todo list on steroids", but it does not come from the tool: it just comes from your increased motivation. And when the novelty wears off, you will find yourself facing the same problems as before, blame the tool again and start looking for a new one. Rinse, repeat...

    So, rather than looking for a technical solution to your problem, you first need to find a better task management method. And as a previous poster wrote:

    1) Read the book "Getting Things Done" (GTD) by David Allen.

    2) There is no 2). The GTD method works very well with just pen and paper, and you can probably implement it with the tools you are currently using.

    Once you are familiar with the GTD method, you may start looking for some GTD specific tool. In that case, I suggest OmniFocus. I reviewed many such tools, but I think OmniFocus is the one that is truest to the method. In particular, it is very important to be able to easily turn a task into a project when you process your inbox. And OmniFocus makes it the easiest: you just drag and drop the task to the project sidebar. All other software make you click extra buttons, input the project title again, and this extra clutter just gets in the way of a smooth inbox processing. OmniFocus is also an iPhone application, that can sync with its desktop counter-part, so you can have access to your GTD system anywhere. Only issue: the desktop version is unfortunately Mac only.

    --
    I code, therefore I am.
    1. Re:Salvation is in the method (GTD) by Beetle+B. · · Score: 2, Insightful

      Once you are familiar with the GTD method, you may start looking for some GTD specific tool

      A warning especially for the Slashdot crowd: GTD will make you itch and itch for optimizing your GTD workflow. Resist the temptation, no matter how strong the itch. Too many technical oriented folks keep trying to improve their software GTD tools (lots of scripts, gluing stuff together, writing your own GTD app for scratch, etc), and the end result is they get little done, because they keep either avoiding GTD until they build the optimal solution (almost never), or they waste too much time constructing that solution rather than, you know, getting things done.

      Just start with some GTD tool out there, start "getting stuff done", and after you get used to it, slowly work through the process of improving it. I use Tracks, which runs on Ruby on Rails and your browser + AJAX is the interface. I'm now thinking of switching to an Org mode solution. Tracks is even missing stuff that is "important" in GTD (no someday/maybe, no agendas, no way to have "waiting for", etc). But it's good enough to get started.

      Lots of software for GTD out there now. Don't try to evaluate all (or even most). My only advice when picking one is that you pick one that makes it easy for you to transfer all your data from that tool to another one you may choose to switch to later on. Although even that may not be a biggie: When switching to Org mode on a test basis, it wasn't too much work just to copy all the stuff manually.

      Another reason to do the above is that almost no one's GTD workflow mirrors the one in the book perfectly. You'll find that deviating a bit from it in certain ways will make you work better. You won't know what your ideal workflow is until you've been trying GTD for a while (and begin to notice headaches created by whatever tools you're using). So if you insist on starting off by building your own tool, you'll soon realize that your tool has irritating flaws, and you'll have to recode a lot of things.

      Oh, and get that filing cabinet. It's unbelievably handy even if you don't follow GTD. If you want to save money, you may find a good enough one in a garage sale. I got mine from a store run by Habitat for Humanity.

      --
      Beetle B.
  26. Re:what we use by Smivs · · Score: 4, Funny

    What do you do to stop the octopi from stealing the coconuts to live in?

    Kick 'em in the tentacles!

  27. OpenGoo by kobaz · · Score: 2, Informative

    I've used so many groupware projects that claim to have excellent task tracking. They all wind up being projects that have a bazillion modules and none of them are much good.

    We stumbled upon OpenGoo. It's a modern web app (very ajaxy), very very fast. It uses Ext, so it's nicely cross browser and is very similar to a desktop app. It has a great ui for very quickly creating tasks and milestones. That's my biggest complaint about many task managers and groupware projects, is that it just takes too damn long to create and manage tasks.

    It also has a contact manager and calendaring, a document manager, time tracking, and reporting. And it does everything quite well. It has due dates and priorities, a messgaeboard for just about every item. You can drag and drop tasks between milestones (projects), you can also tag items. There are configurable workspaces (ie: entirely separate groupings for personal tasks, company tasks, and client tasks). It has a role based permission system, and it's generally just pretty damn awesome.

    opengoo.org

    Disclaimer: I don't work on, or currently contribute to opengoo, I'm just a happy user.

    --

    The goal of computer science is to build something that will last at least until we've finished building it.