Prev: monetary difference between the current progress and the baseline
Next: Basseline work and no resources?
From: sTu_Deimus on 11 May 2010 08:29

Well, finally I've had another stab at this problem. I think I know what
is causing it, but am not really (yet) sure how I need to tackle it.

The problem seems to go away if I remove various predecessor
relationships in the MPP file. Initially I started off removing the
preds for the task and all its parent and immediate sibling tasks, and
that didn't seem to work. Later, after various other hack trials, I went
and removed ALL pred relationships in the file, and that saw the two
tasks (that I was testing with) start working properly.

I think its safe to assume that there may well be some other task with
related predecessor arrangement (eg. distant task still linked to it)
that can explain the problem I had - I will investigate that further
tomorrow. This does however bring me to my area of uncertainty in how we
should manage our data. We traditionally would rely almost explicitly on
preds for sequencing tasks, and then splitting or (ideally) using task
priorities during levelling. Problem is that we currently prefer to just
specify the distribution of remaining work directly into task/resource
usage views (it mirrors our operational reality rather better) - I feel
this leaves the predecessor setup as a rough guide that will ultimately
be over-written by these usage view edits as the project progresses, but
is still a useful guide.

Any thoughts on my general dilemma?

Any thoughts on why MSP would be futzing my data like this in the usage
views?

Further tinkering with the problem just now reveals that:
- initially I'd zero the actual/remaining work for the single user on
that task.
- then enter 10 days of 2 hours remaining work. actual work is zero
everywhere.
- then enter 1 hour of actual work on (say) day 2 - that days remaining
work goes to 1 also.
- that would see the rest of that weeks remaining work zero'd.
- Then, if I touch any days remaining work for the rest of that week,
the actual work would update to match it.
- Interestingly, this did not happen at the same time/week for each
task, but was always the same time/week for any given task.
- I thought it might have something to do with status or current dates
(project info), but it doesn't.

Stu.


--
sTu_Deimus
------------------------------------------------------------------------
sTu_Deimus's Profile: http://forums.techarena.in/members/208670.htm
View this thread: http://forums.techarena.in/microsoft-project/1334267.htm

http://forums.techarena.in

First  |  Prev  | 
Pages: 1 2
Prev: monetary difference between the current progress and the baseline
Next: Basseline work and no resources?