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?"
A combination of Bugzilla and Wiki. Wiki keeps track of backlog. Bugzilla keeps track of tasks.
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
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
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/
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.
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.