What are must haves?
I’m gonna go out on a limb here and NOT request anything special - AT ALL!
WHY?
because I’m very interested in your ‘current’ Project Management as you’ve stated in Post#5 above:
I’ve tried BaseCamp, OmniPlan, CopperProject and a variety of others. None of them have really tickled my fancy.
So, I started delivering a project management portion of every site that I develop. For instance, I’m using a schedule, mockups, documentation, sytle guide and issue log weblog. This allows the client to stay up-to-date with much of the development process but this evolves into a nice maintenance application once the initial build is complete.
Schedule:
The schedule weblog uses the calendar tags of the weblog module to lay out the production schedule.
Documentation
I start most projects with a Statement of Work then I go to Wireframe Mockups and sometimes a variety of other documents are born. This portion ends up being a table with a link to download documents, version numbers and dates.
Mockups
This is mostly used during the design process. I’ve set it up like a blog, so I can post a “first review” and allow the client to comment. Since I allow five revisions with each design, each entry ends showcasing the evolution of the design. It also allows you to capture some very valuable comments from your client. I work with a couple larger companies and it really works well because a variety of stake-holders can give their opinions that you sometimes do not hear during in-person meetings.
Style Guide
With each site, I document the mark-up strategy (commenting, validation, etc…), colors, CSS, images, etc… This style guide allows a central location for future designers/developers and even yourself to learn how the site is structured.
Issue Log
This is the big one! I set this one up blog style with a SAEF to allow the client to fill out issue logs. This is a perfect way to allow clients to supply changes, updates, etc… A client can initiate the issue and then comments allow you to go back and forth with the client until the issue is resolved at which point you can have a custom status to close the issue. This ends up being a TODO list.
Once all this is built, you can supply it with every site you develop. IMHO, since each site has it’s own ‘project management panel’, it begins to be a pretty elegant solution. Also, it makes for a great selling point when you present your methodologies to your client.
Anyway, that is my approach. I hope it’s helpful.