If you're new to this site, then you, like a number of other folks, are probably thinking, "Why is he wasting his time writing yet another project management system? Aren't there already more than enough around?" Well, I'm going to try to answer that question as best as I can...
In using a variety of project management systems, both open source and proprietary, I've come across a few basic types of software: time tracking, time management, task management, and issue tracking. For me, however, none of these types is proper project management.
Categories of Software
Let me illustrate what I think is wrong with each of these categories, and in some cases list software that I've worked with in that category.
Time Tracking
I can't recall a specific application that I've used that is promoted as a project management system, but is actually just a time tracking application, but there probably are a couple around.
The problem with time tracking software is that it tracks time spent, it doesn't plan out your project. It's great to keep track of the time you spent on your project (and it's a feature I'd want in my project management tool), but it is of no use in trying to plan things.
Time Management
Microsoft Project (and it's open source clone, OpenProj) is a classic example of time management. It might have all the facilities to plan things like resources and tasks and sub-tasks, but most project managers just use the Gantt chart to see how long the project is estimated to take.
This is not proper project management. Project management (in my opinion) needs to have milestones for each project, and also a bug/issue tracking side to it. Microsoft Project has neither, though by using tasks and subtasks you can simulate the milestones > task lists > tasks hierarchy. Microsoft Project doesn't track time taken either, preferring to use a % done system instead.
Task Management
Basecamp and activeCollab (the old open source version, at least) both implement task management. You can use them to create milestones and task lists and tasks, which is great. With Basecamp you can even track how long a task has taken.
Neither of them, however, has bug or issue tracking. Issue tracking is fairly essential in project management, it's part of the Testing and Support phases of the project. Once your software has been completed, you'll usually have a number of people testing it, and then once it's out in the field, you'll want to be able to accept bug reports and track them.
Issue Tracking
There are a few applications that fall into this category. Some are marketed as project management, others just as issue tracking, though I think a lot of them get used as project management tools. We use RT:RequestTracker at work, but there are others like Trac and Redmine.
These tools don't implement the task management and time tracking parts of project management. This means that while they can be massaged to work (and in Trac's case, they provide "milestones") like a task management system, but in most cases you're using the wrong tool for the job.
Project Management Software
That said and done, there are some applications that do give you a fuller project management system. However, I've generally found them lacking in one or more areas. For example, dotProject is actually quite complete. It contains task management as well as issue tracking. One of dotProject's problems, though, is that it's workflow is confusing and unintuitive.
Layout & Usability
A number of project management systems suffer from bad layout and usability. Navigation is sparse, and buttons are not in the places you'd expect them to be. Web-based systems like dotProject don't make use of AJAX, and the navigation in systems like Trac is confusing.
Workflow
dotProject (when I looked at it last) is a classic example of bad workflow. You could track the time you took to complete a task, but in order to do that, you had to jump through hoops and click through about 3 pages from the task list to get to the point where you could type in the hours you spent on the task in question. Other systems don't even have a workflow.
Design
Yes, design is not everything, and it has no bearing on functionality, but I'm sick and tired of using a system that looks like it was hauled out from the garbage can. Design plays a role in usability and layout, and an effective design can mean that your users are not scared of dealing with this ugly system. Keeping your users happy can keep them in the project management tool for longer, meaning you get better usage out of the tool, and better management of your projects.
Goals for Project HQ
So my main goal for Project HQ is to produce a system that is easy on the eye, simple and intuitive to use, covers task management, time tracking, and issue tracking, and also includes collaborative features like a wiki.
I'd also like to add other features like VCS integration (commit a bug fix and it closes the ticket), uploading files and documents, bookmarks ("starred" items), and e-mail notifications.
I consult project managers and developers using various project management solutions to see where and how Project HQ can improve over existing products, and where it needs to change to work better. This helps me to make Project HQ more than just a solution for me, but for folks who use these systems on a daily basis. If you'd like to try it out, and have some feedback to give me, please contact me via the contact form on the site.
