following aggressive target duration schedules to reduce over–allocation of time, placing buffers at more
strategic locations in the project timeline, avoiding multitasking because there are switching costs,
emphasizing resources and the contention for resources when planning, and finally tracking the status of
buffers managing both their depletion and replenishment.
Critical chain scheduling eliminates any buffers from the individual activities; instead, a general project
buffer is created. Eliminating individual buffers helps to decrease the entire duration of the project, while
the project buffer protects the final due date. The removal of individual buffers serves the additional
purpose of discouraging people from engaging in multitasking or other distractions. As the duration
estimates (without the individual buffers) are very aggressive, people focus on the task at hand in order to
finish the task in the allotted time.
In addition to the project buffer, critical chain scheduling uses feeding buffers to protect the activities on
the critical path. Usually, in complex projects, many noncritical activities feed into critical activities. As
the individual safety buffers are eliminated using critical chain scheduling, a change in duration of a
noncritical activity feeding into a critical activity would influence the critical path and, thus, the duration
of the entire project. To prevent this, a feeding buffer is added to any noncritical activity feeding into a
critical activity. The project manager can easily monitor the use of the feeding buffers and the project
buffer to determine whether the project is on schedule. Project management software frequently employs
third-party add-ons for critical chain scheduling.
When using any of these techniques, a project manager should always monitor the project calendars and
resource calendars. In a large software development project of a multinational corporation, virtual teams
located in different regions of the world might be working on completing a certain task; thus, teams
could work in three continuous shifts. The resource calendar would specify these working times. On the
other hand, the client organization might be available only during certain times, so that, for example,
during requirements generation, the project team members cannot get in contact with it. Such times
would be specified in the project calendar.
Another factor to be considered during schedule network analysis is the use of leads and lags. In the
activity sequencing stage, the leads and lags of the different activities have been established. To review, a
lead is the time between the start of one activity and the start of an overlapping activity; a lag is the time
between the finish of one activity and the start of a succeeding activity. As these leads and lags can
significantly influence the schedule, their use should be carefully double-checked to minimize potentially
negative impacts on the schedule.