HELP!  I'm a new PM in a slightly strange situation.  I am aware of PM methodologies, familiar with many PM softwares, and have previous project tracking experience .  However, I have never had to actually guesstimate time requirements for technical activities until now (previous tracking involved accounting/auditing), and I am at a loss.  Also, my experience in the past always involved deadlines given first, as in "Here's the new software/hardware, it has to work by next week."  I've never personally tracked the time it has taken, say, to install and configure Quickbooks, or research, purchase and install a new phone system.  I'm a salaried employee and just worked until it was done.

Most of the online and hardcopy resources I have consulted give assistance on project time estimates with the underlying "given" that someone (either the PM or the tech) has the knowledge of how long each task/subtask takes.  What I need is some kind of average starting point for technical projects, i.e., assuming no knowledge of how long the task will take.  Does such a thing exist?  If not, which tools do you recommend I use to guesstimate?

Any assistance is greatly appreciated!

Valerie,

First, relax.  You have some of the best experts in the field of estimating...your project team, enlist their help.  (See visuals of this note in the attached PowerPoint) 

Assemble the team after your kickoff meeting and go over the scope of the project.  Hand out sticky pads to the team.  On a whiteboard or large piece of paper, start with your phases or the top level of your WBS and have them list all tasks to be accomplished during the phase.  Each sticky pad sheet should list the name of the task/activity, what role should be assigned (can be many roles) and an approximate estimate of the time to accomplish the activity.  If you can't give a good estimate, break the task into more detail.  Try to keep the detail level at the day (8 hour) level.  Arrange your sticky pad sheets into a logical order with lines or some type of linkage (see PowerPoint).  Add up the hours and transfer the tasks to your scheduling tool.  You now have an approximate estimate probably MUCH better than you would do on your own.  As you manage more projects, you will have a history for making better estimates and soon become an estimating pro yourself!  Don't ever try this on your own.  Use your team!

Perhaps this link will help!

Articles on Estimating