Task Type Concern

[PMinPA]

Project Server 2007 rollout underway and our (very large, global) company has
decided (with advice from a large Project Server integrator) to mandate that
all tasks in new enterprise templates use only fixed duration with effort
driven = yes. This seems contrary to best practices used in successive
desktop versions of Microsoft Project over the years that will seemingly lead
to lots of problematic recalculations. Question: What are the benefits of
using this configuration in Project Server for all projects?

 

[Jack Dahlgren]

It all depends on the type of work you are scheduling. I'm partial to fixed
duration as a standard because it is the most stable and usable by novice
users. In fact, it leads to fewer mis-understood recalculations. Users set
duration then work and units vary proportionally. Very simple. I'd leave
effort driven off though unless the work is fungible.

But there are times and places for all approaches. Without knowing the
specifics, no one can judge.

What makes you think it is a bad recommendation?

-Jack Dahlgren

 

[Gary L. Chefetz]

Speaking in theoretical terms, you are correct that Fixed Duration and
Effort Driven, together, is somewhat of an oxymoron. Fixed duration implies
that no matter what you do, the duration stays the same, while Effort Driven
implies that if you throw more labor at the job, you can shorten the
duration, which in the case of a Fixed Duration task, doesn't ever move.

But, like Jack says, maybe the point of this standard isn't obvious, but
practical in your situation.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com