TABLE OF CONTENTS This chapter describes the process of developing the single-project-management system to satisfy the system requirements identified in the previous chapters and further detailed herein. Although presented as a forward-moving process from requirements to design, the actual process, as is the case with nearly all designs, was iterative; that is, various design solutions were proposed and tested against the requirements until a suitable working system resulted.
Table 4.1 illustrates the requirements for an effective project-management system, following the method of Joseph Juran [1]. The table presents the requirements in a hierarchy, starting with the top-level necessary conditions for project performance. These include the three technical requirements for the project (scope, cost, and schedule) and the requirement for stakeholder satisfaction. Project stakeholders always include at least the project customer and the project team and may include many others (e.g., subcontractors, stockholders, regulators, neighbors, government, or other groups or institutions).
These are the requirements I use in defining CCPM. Many advocates of TOC and critical chain do not deal with the full scope of these requirements, for one or more of several reasons. Some are simply not aware of the full scope of requirements that the project system must meet, and they focus only on the part that Dr. Eliyahu Goldratt addresses. Others may not think they are necessary. I believe some organizations fail to achieve success with CCPM because they do not satisfy all of the necessary requirements for effective project delivery.
