Now we all know that the finish date a project is automatically calculated by Project and might not necessarily be the due date. If the finish date is before the due date, you have some buffer, if the finish date is after the due date, you have a problem. Let’s assume you are in the first case – it is important to track this buffer and I’ve found manually scheduled tasks are useful for this since they won’t automatically move but they’ll warn you when there is a problem.
Let’s say you have this project (this will work for all projects, just make sure you have a milestone representing the project finish that all task chains are connected to):
My project finish date is January 9th but I actually don’t have to be done until the 13th so I have a few days of buffer. To represent that I add a new manually scheduled task with the Project Finish milestone as the predecessor and the end date as 1/13:
You can now easily tell that you have 4 days of buffer.
Now say that task 4 takes 3 days instead of 1 day. Your schedule will look like this:
Notice how the buffer tasks didn’t move but you get a warning that there is an issue. Now go in and for the Buffer task, right-click and select Respect Links. This will push the task out. Now you need to decrement the duration until the finish date is once again the 13th:
So you can now tell from task 4 slipping that you only have 2 days left of buffer.
I find that manually having to update your buffer task helps to make you more aware of when you are using up buffer. You can use this same technique on individual task chains, etc., if you want. Additionally, if you want to make sure you remember the deadline, you can set a deadline on the buffer task to make sure you always adjust the buffer back to it.
Learn more about this and other scheduling tips by attending the Microsoft Project Conference 2012 in Phoenix, AZ March 19th-22nd.