Zane said:
Can someone elaborate on how the EPM (2003) solution handle the following:
a.. Double-time entry - if we want to get project-level metrics
a.. Reliable delivery of all email notifications
a.. Over-delivery of email notifications
a.. Transferring electronic assets - particularly with off-site teams
a.. Usability of some forms
a.. Effective Work Breakdown Structures to communicate with the team -
loaded as Tasks
We are trying to evaluate whether Project 2003 Server / Pro is a fit for us.
Thanks.
Zane, I will give it a shot, based on PS 2002 and PS 2003 experience.
Double-time entry - if we want to get project-level metrics
I am assuming you have a time entry system that you are already using.
If you want to collect project level metrics, you must define the
kind of data of you want to collect, use the PWA timesheet to collect
actuals, and use Project Server to aggregate and present your metrics.
If you are using an existing time entry system, this would require
double entry of time, but it is also possible to export time from
Project Server.
Reliable delivery of all email notifications
I have never seen a problem with this, assuming correct configuration
and a reliable email server.
Over-delivery of email notifications
This can be controlled to a certain extent via process and via
settings. In my experience, some people complain about too many
messages from Project Server but most do not. Some people (project
managers and team members both) overuse the "alert" features.
Transferring electronic assets - particularly with off-site teams
Project Server is primarilly a collaborative tool and using Windows
SharePoint Services, it is very easy to maintain a store of your
electronic assets.
Usability of some forms
Need to be more specific here. Project Server does a number of things
well. Printing is not one of them. You can print grids or export
them to Excel.
Effective Work Breakdown Structures to communicate with the team -
loaded as Tasks
Not quite sure I know what you are asking, but I will guess that you
are talking about assigning tasks to team members at the appropriate
level. Team members see the project/phase/task they are assigned to
in the team sheet. They don't have to wade through a bunch of tasks,
as they only see the ones they need to work. They may (or may not)
see other projects/tasks in the Project Center views, depending on how
the server is configured.
Hope this helps.
Mark
m a r k s e v e r e t t 5 5 5 @5 5 5 c o m c a s t D O T n e t
(remove the numbers).
