In a resource loaded effort driven schedule. I have asked project managers to record actual s in the following order:
Actual Start, Actual Work, Remaining Work, Actual Finish. Anyone see any issues with this order in Microsoft Project 2013, should the PMs have an any situations when this order would cause issues?
Denise, I’ll start with telling you that I “think” that will work just fine. I’ve used something similar to that using duration fields. You may not need to enter actual finish once remaining work is zero, but watch to make sure actual/remaining hours don’t change when you overwrite Actual Finish (sorry, too many task configuration options for me to be sure). I do have a question for you. What is the source and format of the data you are using to enter actual hours. If you are getting data as total actual hours by task then that method will work fine. I quite often see this as resource actual hours by task for the period (like from a time tracking system). If that’s the case then they will need to add the additional hours to the current actual hours from prior periods. You might want to use a version of the Resource Usage view (or Task Usage if you are getting the information by task) and enter actual work for that period (usually weekly). It might be easier and you won’t have to enter actual start or actual finish as the finish will be accurate to the timescale entry. Hope that helps. Let me know if this option makes sense or you have any questions.
A good many vabaulles you’ve given me.