K
Kerry
I've read many questions here on this topic, in this group. I have a small
understanding of scheduling engine, maybe that's why I'm confused. If I set a
task to fixed duration, not effort driven, and put a finish no later than
constraint on a task, why do finish dates move when applying effort to the
task. I've already told Project to take efffort out of the equation. So, why
is the scheduling engine still using it for scheduling? If it's strictly for
resource allocations, then change the allocation, not the date.
We using SCRUM methodology, as a result, many dates are fixed. Multiple
tasks are time boxed, although not all. So, some tasks I need project to do
it's thing, and move dates based on actuals(effort driven). For fixed
duration tasks, that aren't effort driven, I still need record the hours, for
cost purposes.
To me, it's a bug. The scheduling engine is making assumptions that it
needs to do something, but I've already told it not to. Anyone else see this
as a problem?
understanding of scheduling engine, maybe that's why I'm confused. If I set a
task to fixed duration, not effort driven, and put a finish no later than
constraint on a task, why do finish dates move when applying effort to the
task. I've already told Project to take efffort out of the equation. So, why
is the scheduling engine still using it for scheduling? If it's strictly for
resource allocations, then change the allocation, not the date.
We using SCRUM methodology, as a result, many dates are fixed. Multiple
tasks are time boxed, although not all. So, some tasks I need project to do
it's thing, and move dates based on actuals(effort driven). For fixed
duration tasks, that aren't effort driven, I still need record the hours, for
cost purposes.
To me, it's a bug. The scheduling engine is making assumptions that it
needs to do something, but I've already told it not to. Anyone else see this
as a problem?