Non-Microsoft project management tool

[hanasaki]

MS Project is just a tool.  You can debate its quality if you like but 
its just a tool.  Get a real Project Manager to ensure that the tool is 
correctly applied and used.  MS Project is not "implemented".  A proces 
is implemented and the PM uses MS Project to measure/monitor the process 
as applied to a specific project.  A PM gets a good salary and is worth 
it.  A PM is trained and has experience.  They are not simply "book 
smart/read".
	www.pmi.org

"find out what they really want" - Very good point.  Its called 
requirements gathering.  Oh, don't forget to validate the requirements 
and make sure they aren't requirements to implement a solution that 
someone has in mind.  Look for business requirements and filter out 
implementation requirements.  Customers often sneak these in and don't 
even know it.

If you don't have, and correctly use, a software methodology, your hosed 
from before day one!
	http://www.sei.cmu.edu/
	http://www.rational.com/products/rup/index.jsp
	http://www.sse-cmm.org/

<end rant>

Wondering where my views come from?  12+ years in Software Engineering 
and a Masters in Project Management.

Mike Coleman wrote:
> "I am Spartacus" <spartacus at home.aafp.org> writes:
> 
>>okay, so the higher-ups have warned me that in an effort to better track our
>>projects at the office, they are thinking of implementing Microsoft Project
>>and requiring that we manage and update our programming projects through
>>this software.
> 
> 
> I would stop right here and try to figure out what's really going on.  What
> does "track" mean?  The executives feel that the programming staff is goofing
> off?
> 
> I've seen and worked on a few projects managed by Microsoft Project and
> they're invariably train wrecks.  Not because Project is a bad piece of
> software (though that may be), but rather because it is generally superfluous
> and counterproductive paper-shuffling, as applied in reality.  That your
> higher-ups doesn't understand this is a bad sign.
> 
> Ideally, find out what they *really* want and have someone skilled in software
> development liaise with them to get it, if it's reasonable/possible.
> 
> As for tools, I'd start with a simple task list (with minimal due date and
> priority information) and wait until you outgrow that.
> 
> Mike
> 
-- 
= hanasaki at hanaden.com                                          =
=     Spam : Just Say NO!                                       =