Think about it a bit - it is physically impossible to complete work for the
future as scheduled unless you have a time machine. If I have a 5 day task
that is scheduled for the second week of February and it is complete as of
yesterday, 20 Jan, I did not do the work as scheduled. I rescheduled it to
start 15 Jan and then did the work. (Whether the written plan reflects the
schedule change or not, that is what in fact happened.) When you post
actual progress in your plan, use the "update tasks" tools only if the work
took place on the dates the schedule called for it to take place (and took
exactly as long to complete as the schedule estimated it would). If it
happened earlier or later than those scheduled dates, use the Tracking table
to enter Actual Start and Actual Finish (Use those fields - DO NOT update
the plain Start and Finish fields in the Gantt Chart by hand!) so that they
conform to what has actually taken place. As Mike said in another post -
the project file should ALWAYS reflect phyiscal realities.
By the way, % Complete is not ACWP/BAC, it is BCWP/BAC. The only time it
would be ACWP is if every task required exactly the number of man-hours to
complete that you had estimated it would and that is rarely true. Look at
one task, scheduled for 40 hours using a cost of $1 per hour as you are.
BAC = 40. We finish the task as scheduled. ACWP=40, BCWP=40 and
ACWP/BAC=BCWP/BAC=100% But let's say we mis-estimated and we finished the
task in only three days. ACWP=24, BCWP=40 because our budget called for 40
hours of work and we've done all the work, ACWP/BAC shows the task is 75%
done, not correct since we have actually created all of what the task was
required to create. BCWP/BAC = 100% done which is the acturate indicator.
BCWP/BAC shows schedule performance
ACWP/BAC shows budget performance
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs