Moving Remaining Work

[hinrgsunshine2]

Project Server 2003
Managed Time Periods, with resources entering actual work each week

We run a query out of the Portfolio Analyzer that shows how much
"remaining work" a resource has (work - acutal work) on
a specific project. This is done for each quarter to show what didn't get
done
or was overplanned. The project manager needs to then review this and
decide to either purge the work that wasn't done or move it forward into the
current/future quarters.

Let's say a resource shows that he has the following planned work, on 1
task, that spans several quarters:
100 hours in Q1
100 hours in Q2
100 hours in Q3
In Q1 he only does 50 hours. It's now Q2. That 50 hours that didn't get
done and needs to either move into Q2 or get purged.

If the project manager decides to purge the remaining work we
been using the task usage view in MS Project Pro 2003
to compare Actual Work Protected to Work. Where there is a variance in the
past
we edit the work to match the actual work... essentially purging work that
wasn't performed. We republish and we're done. What we're seeing happen
is that when we do this, then we sync to actuals, the work comes back and no
longer matches actual work protected.

There's GOT to be an easier way for us to get rid of the
overplanned/un-performed work in the past.

 

[Gary L. Chefetz [MVP]]

You should be adjusting remaining work. Resources should be doing this as
they report progress. Are you using Project Server and PWA to collect
status?

--

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

 

[hinrgsunshine2]

Yes, we are using Project Server and PWA to collect status. Default method for
reporting progress on tasks is set to "Hours of work done per day or per
week: Resources report the hours worked on each task during each time period.
"

Resources submitting time are only allowed to submit actual work, not update
remaining work. We removed Remaining Work from timesheets for 3 reasons:

we did not want resources to have the ability to increase the work budget
without oversight/authorization

resources more often than not, do not update the remaining work (wish it
were a mandatory field in PWA)

no easy way for a timesheet approver to see that someone updated the
the remaining work. So, it wasn't being scrutinized.