Guidance on weekly update process

[gac]

I track several software development projects in a single MSP. I only track
work & dates, not cost. My MSP is 350+ tasks long, with about 30 resources.

After updating actuals each week (week=Sat-Fri) for all resources, I
reschedule any uncompleted work to start after the Friday of updated week,
then re-level resources. Is the weekly update approach sound? (I don't
track costs)

I then review my variances from baseline (mostly Work & Finish) and use
those findings (et al) in my status reports to senior management. I also
report tasks which are / aren't starting / finishing on time. (as compared to
start / finish) Although I now have mechanisms in place to monitor ongoing
slippages from my baseline, I don't know what features of MSP to best use.
What views, filters, columns, etc. Right now, I primarily rely on GANTT
and custom filters. Any suggestions would help.

 

[Jan De Messemaeker]

Hi,

First a small suggestion on your process.
Best is to clear leveling before Reschedule work.
Indeed, when a task has been shifted far away by the previous leveling,
Reschedule work will ignore it, and the new leveling may well place it
before the tracking date.

Take a look at the Tracking gantt and the Variance Table.

HTH

 

[gac]

Jan, thanks for your prompt and accurate help on this and my other recent
post.