Migrating Existing Schedules to Project Server

[Roxanne]

I have some questions, as my organization is prepping to use Project Server,
and we are finishing much of the config settings. We don't have any projects
in Server right now. And all of our projects have been using Project Pro, but
haven't created WBS down to the task level, phases for SDLC weren't used,
they haven't used resource pool, with attached hourly rates..etc. So, we have
also established new Cost Mangement procedures, and to align with this we are
wondering best approach for schedules in progress. Do we baseline their
existing schedules, knowing that there will be much discrepancy in the
schedules, or do create related "new" schedules starting on date of
implemention of cost processes rolling out, and just align the completed
project with the Project Server "new" project...any ideas appreciated -

 

[Rod Gill]

If I was you I would forget about Project Server for the moment. The most
important things to get right are the processes for managing your projects,
how you need to govern your PM processes and how you will manage resources,
project priorities etc etc. Then look to how the tool (Project Server) can
support you and your processes. You will also get a god idea of the training
your people need in Project, project management and indeed in scheduling.
The tool on its own can do little. As a support for trained people and
working processes it can add good value.

From your post I read that you are looking for ways to use the tool that
will help your projects, but that's the cart before the horse!

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[Gary Chefetz]

Roxanne:

There isn't a "right" answer to this, there's only what's "right for you,"
or your organization. With that said, you can choose to use the existing
plans. If you do that, you want to close out all of the portions of the
schedule that are in the past, and build out the future portion of the plan
to the extent necessary to support your selected tracking method, before
importing them to the server. A best practice approach is to start with
one, and learn from the process. Keep in mind that you're making a huge
organizational maturity leap when implementing an EPM tool.