Limits of Creating Projects in Project Web Access

P

Paul K

We want to try and keep the Project Pro client licenses down and want to know
what are the limits to using Project Web Access for Creating Projects. Does
anyone know where there is documentation on this? Or can anyone give me
guidance about what kind of limits there are in terms of tasks, resources etc.

Thanks,
Paul
 
J

James Fraser

We want to try and keep the Project Pro client licenses down and want to know
what are the limits to using Project Web Access for Creating Projects. Does
anyone know where there is documentation on this? Or can anyone give me
guidance about what kind of limits there are in terms of tasks, resources etc.

Thanks,
Paul
Click to expand...

While this capability is exciting and has a fair amount of potential,
it's gotten poor reviews initially: Projects created within PWA may
only have one resource assigned per task, and only at 100%. This
limitation has been enough to cause most users to keep project
creation in Project Pro.


James Fraser
 
B

Bill Busby

The activity plans created in Project Web Acess are termed lightweight
projects and have significant limitations. As James mentioned you can only
assign one resource per task. That alone was enough for us to initially ban
their use. We did eventually implement them but only by mandating they have
no tasks and assign resources at the top level. Even if you have tasks they
have very little detail.

This is a potentially very useful feature that, if Microsoft matures the
capability to just have multiple resources on one task would be incredibly
useful. I'm not privy to why certain design decisions are made (would
certainly have been screaming at the top of my lungs if anyone would listen
on this one) but it's possible that having this feature too much like a real
project would reduce demand for the full blown Project Pro and have a
negative effect on revenue. Much as you've been considering.
 
P

Paul K

Is there any documentation on the limits?

Bill Busby said:
The activity plans created in Project Web Acess are termed lightweight
projects and have significant limitations. As James mentioned you can only
assign one resource per task. That alone was enough for us to initially ban
their use. We did eventually implement them but only by mandating they have
no tasks and assign resources at the top level. Even if you have tasks they
have very little detail.

This is a potentially very useful feature that, if Microsoft matures the
capability to just have multiple resources on one task would be incredibly
useful. I'm not privy to why certain design decisions are made (would
certainly have been screaming at the top of my lungs if anyone would listen
on this one) but it's possible that having this feature too much like a real
project would reduce demand for the full blown Project Pro and have a
negative effect on revenue. Much as you've been considering.
Click to expand...
 
G

Gary L. Chefetz [MVP]

Paul:

They are *very limited.* You can't get around having a Pro license for
everyone who has manages a schedule in Project Server. Do not try to use web
access as a substitute for the Project Pro client, as that is a non-starter.
Use this for creating proposals and activity plans only. Treat proposals as
"yet to be detailed" projects.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
 
Top