Critical Chain (novel)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Critical Chain
CriticalChain.jpg
First edition cover
Author Eliyahu Goldratt
Country United States
Language English
Subject Project Management
Genre Business Novel
Publisher North River Press
Publication date
4 September 1997
Media type Print (paperback)
Pages 246 pp (first edition, paperback)
ISBN ISBN 0-88427-153-6 (first edition, paperback)
OCLC 36781362

Critical Chain is a novel by Dr. Eliyahu Goldratt using the Critical Chain theory of Project Management as the major theme. It is really a teaching method for the theory.

Plot introduction[edit]

Like Goldratt’s book The Goal, Critical Chain is written as a novel, not like a project manager's how-to guide. This book is a story about a professor trying to attain his tenure at a university's business school. The plot is used to maintain interest in the subject and provide a real life feel to the book. It provides plenty of real-world examples. The plot of the novel is fourfold:

  1. A professor trying to become tenured,
  2. A business school's struggle to improve enrollment,
  3. Teaching philosophy,
  4. Applying the Theory of Constraints to project management

The goal of the book is the last point, but Goldratt makes it clear that educational systems must change to better accommodate the quickly changing world of business.

The book walks the reader through a series of steps to establish the principles for the discussion. It is written for someone with a modicum of project management background.

The book starts by pointing out the problems with how time estimates are normally done on projects. It then provides a primer on the Theory of Constraints and an example of its implementation in a steel mill. With the foundation set, it proceeds to show how the Theory of Constraints can be applied to schedule generation, resources constraints and multiple projects.

Plot summary[edit]

Scheduling Estimates[edit]

Goldratt claims that the current method of generating task time estimates is the primary reason for increased expense of projects and their inability to finish on time. The commonly accepted principle is to add safety (aka: pad or slop) to generate a task time length that will essentially guarantee the step gets completed. He asserts that estimates for a task are based on individuals providing values that they feel will give them an 80-90% chance of completing the step, these estimates are further padded by managers above this person creating a length of time to complete a task that is excessive - as much as 200% of the actual time required. It is this excessive padding that has the opposite effect - guaranteeing the task will run full term or late. As counter intuitive as this seems, he provides examples of why this is the case. This predisposes the people on the project to consume the time estimate by:

  1. Triggering the "student syndrome" in the resource assigned to the task - they have more than enough time to do the task, therefore they start the task late using up all the safety.
  2. Encouraging multitasking. The safety is added knowing that the resource will not be able to focus on the task and hence encouraged to multitask on multiple projects at a time, which significantly impacts all projects.
  3. Not claiming early completion. In order to preserve the safety concept in future projects, resources do not report tasks completed early. Obviously, though, there is no way to hide a late completion.

Theory of Constraints Primer[edit]

The book presents a primer for Theory of Constraints. This is done in the form of a lecture by a professor who has recently returned from a sabbatical at a large conglomerate that uses the Theory of Constraints. The discussion focuses on the current methods of measuring success at a work center (cost and throughput) and shows how they are contradictory to the success of the production line as a whole.

The book enumerates the five principle steps of the Theory of Constraints:

  1. Identify. Identify the bottleneck of the system.
  2. Exploit. Exploit this bottleneck, making its throughput efficient by changing processes, equipment maintenance procedures, training, policies, etc.
  3. Subordinate: Subordinate the throughput of all other work centers to this work center.
  4. Elevate. Invest in this work center to increase its throughput - add equipment, manpower, etc.
  5. Inertia. Start the process over on the line to determine the new bottleneck.

This philosophy keeps the cost and throughput models at odds with one another since the subordination process necessarily decreases efficiency. Hence, evaluation criteria for properly managing a work center must change to properly reward the organization’s success.

The book points out this conflict with respect to an axiom in the Theory of Constraints that states that if two concepts are in direct conflict, then there is an assumption as part of those concepts that is incorrect.

Steel Mill Example[edit]

To illustrate, the book uses an example of a steel mill with significant production problems, excess inventory and cost issues. It methodically assigns all the issues of the plant to the method in which success of a work center is measured. The errant assumption is efficiency being measured by tons of steel per hour. The flaw in the measurement is that not all material takes the same length of time to produce and not all work centers have the same throughput. It concludes the sources of the problems for the steel mill are:

Issue Causes
Yard inventory
  • Over producing product to minimize set-up impact,
  • Producing excess high-throughput material
  • Instead of sitting idle, produce unneeded product.
Raw material shortage
  • Over consumption of material to produce material in inventory

After subordination, the key is to maintain a small buffer of material in front of the bottleneck to ensure it never stops producing due to lack of material.

Basic Principles[edit]

After laying this groundwork, the book turns to applying this to Project Management. After declaring the constraint to be the schedule's critical path, the book maps out a set of terms. The result is:

Production term Project term
Work center Task
Product Time
Pre-work center inventory Work buffer from the feeding tasks of the critical path
Bottleneck work center Bottleneck resource

It proposes a method of schedule generation where all tasks are estimated at a reasonable time for completion. This would be a time estimate that would give the resource a 50%-60% chance of completing the task on time. The theory being that one task may take less than its estimated time but another may take more - on the average evening out. Since there is no safety, the conditions above that cause misuse of time on the task do not exist.

Safety is not added to individual tasks. Safety is added to the project as a whole (at the end) or to the end of a sequence of tasks feeding the critical path.

Resources Influences[edit]

Using numerous analogies and examples, the concept of a resource buffer is introduced. This concept claims that one must ensure the resource bottleneck on the critical path is always busy and stays focused. They should be:

  • Kept on task. In other words, minimize multitasking
  • Be ready for the assignment; even if it means they are idle waiting for dependencies to complete.

The book introduces increasingly complex situations to remove the non-practical classroom approach until it reaches two common project situations:

  • A bottleneck resource on the critical path and non-critical paths,
  • Multiple projects contending for constrained resources,

The book emphasizes that the project manager has to understand that he or she is not working with absolutes. Resolution of these issues are not absolute. The time estimates are just that - estimates - they cannot be treated as absolute times. This is essential for the following two points.

Resource Constraints[edit]

A project example is given with a single bottlenecked resource on multiple paths. Since this resource is over utilized on multiple paths its tasks need to be considered when determining the project duration. This results in the introduction of the term critical chain - the aggregate of the critical path and the constrained resource leveled tasks.

Multiple Projects[edit]

Projects are going to use common resources. Organizations need to accommodate parallel projects while adhering to the Theory of Constraints concepts. This requires developing a prioritization scheme for the resource to determine the correct order to do work (i.e. proportion of the project buffer remaining). As before, once the scheme has been developed, the resource needs to be focused (not multitasking) on completing the task as soon as possible.

Cost of money[edit]

The book closes by introducing a concept for a method for determining which projects should be selected for execution. It is based on looking at the investment in each project in terms of money-days. Money-days is the product of the investment in the project and its duration.

Reviews and analysis[edit]

The book was reviewed by a number of academic and business journals including Harvard Business Review [1] and IIE Transactions.[2] In addition, a number of academics have studied Critical Chain Project Management and shown that while the packaging of the content is novel, the ideas are not necessarily original and in some cases, not advisable.[3][4][5][6]

References[edit]

  1. ^ J. Elton, J. Roe. 1998. "Bringing Discipline to Project Management." Harvard Business Review, 76(2), 153-159.
  2. ^ K.N. McKay, T.E. Morton. 1998. "Review: Critical Chain." IIE Transactions, 30(8), 759-762.
  3. ^ W. Herroelen, R. Leus. 2001. "On the merits and pitfalls of critical chain scheduling." Journal of Operations Management, 19, 559-577.
  4. ^ W. Herroelen, R. Leus, E. Demeulemeester. 2002. "Critical chain project scheduling: Do not oversimplify." Project Management, 33(4), 48-60.
  5. ^ T. Raz, R. Barnes, D. Dvir. 2003. "A Critical Look at the Critical Chain Project Management." Project Management Journal, 34(4), 24-32.
  6. ^ D. Trietsch. 2005. "Why a Critical Path by Any Other Name Would Smell Less Sweet? Towards a Holistic Approach to PERT/CPM." Project Management Journal, 36(1), 27-36.

External links[edit]