The last time I read up on the Critical Chain method, the papers were riddled with jargon such as “evaporating clouds”, “self-reinforcing negative feedback loops”, “bad multitasking”, “leverage points” and “buffers”. What I got out of it after distilling it into laymans terms was the following (if I am wrong, somebody please correct me):
- Estimate tasks / activities without any fat.
- Create a well defined (well connected) critical path schedule where all logical (hard) dependencies are specified.
- Resource level the schedule.
- Add “buffer tasks/activities” (fat) to the critical and near critical tasks so that you don’t
commit to the true (lean estimate) critical path. The fat will shrink as the schedule slips.
- Implement a feedback mechanism that keeps everyone informed of the progress and changing criticality in the schedule.
- Establish clear priorities. Ensure that workers finish one task before starting another.
Of the above, the only items that are specific to Critical Chain is the addition of the "buffer management", which to my mind is the same thing as float management in CPM except for the fact that you actually may build some fat in your critical path schedule.
Personally, I prefer to schedule without fat and manage the project to the most aggressive objective. It would seem to me that building fat into your schedule is just setting yourself up for Parkinsons Law, "Work expands to fill the time available."
Bernard Ertl
InterPlan Systems Inc. - Project Management Software, Project Planning Software