WEB client vs Project Pro client

[VIDRO]

We have purchased Project server, now there are a few questions that have
come about.
What can you do with the Project Pro client that you cannot do with the
Project server WEB client?
In a nut shell management wants to create and manage project/proposal
through the WEB interface and not have to worry about installing client
software

 

[Dale Howard [MVP]]

Vidro --

Assuming you are using Project Server 2007, then you can create and manage
very simple projects ("lightweight projects") in PWA. There are many
limitations for using these lightweight projects, so many in fact, that I
cannot imagine using them for the average types of projects that most people
manage. For full-featured project management, your PM's would need to use
Project Professional 2007. Hope this helps.

 

[VIDRO]

Yes it does.
Do we lose any flexibility in messaging integration.
It seems we are confused with resources that are “Proposed†versus
“committedâ€.
In my thinking, a resource should not be notified or associated with a
project until the project has been “blessedâ€.
What I am seeing is if a Proposed resources is proposed and not committed
when that client syncs with the project it will sync the proposed task with
the proposed resource.
Shouldn’t the resources Calendar only be populate with the task after the
proposal has been “blessedâ€.
I think the real problem is I do not understand how project views its
resources.

If I try to create a Resource group and view the “availability†of a
specific resource, even if that resource calendar has something else
schedule (not associated with Project server) the “availability†still shows
them as being available for a proposed task.

 

[Dale Howard [MVP]]

VIDRO --

The way that Project Server 2007 is supposed to work is as follows:

1. You add a resource as Proposed to the project team.
2. You assign the resource to one or more tasks in the project.
3. You publish the project.
4. The tasks do not appear on the resource's My Tasks page in PWA.

Unfortunately, a bug in Project Server 2007 prevents #4 above. Instead, the
tasks appear on the resource's My Tasks page anyway. Therefore, using
Proposed or Committed doesn't really serve much purpose until Microsoft
fixes this bug.

Also, when you view a resource's availaility, Project Server 2007 only shows
you information from within the system. It doesn't show work outside of
Project Server, such as appointments on a resource's calendar in Outlook.
Hope this helps.

 

[VIDRO]

Yes, you have been a big help. Very Good

VIDRO --

The way that Project Server 2007 is supposed to work is as follows:

1. You add a resource as Proposed to the project team.
2. You assign the resource to one or more tasks in the project.
3. You publish the project.
4. The tasks do not appear on the resource's My Tasks page in PWA.

Unfortunately, a bug in Project Server 2007 prevents #4 above. Instead, the
tasks appear on the resource's My Tasks page anyway. Therefore, using
Proposed or Committed doesn't really serve much purpose until Microsoft
fixes this bug.

Also, when you view a resource's availaility, Project Server 2007 only shows
you information from within the system. It doesn't show work outside of
Project Server, such as appointments on a resource's calendar in Outlook.
Hope this helps.

 

[Dale Howard [MVP]]

VIDRO --

You are more than welcome for the help, my friend!