<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Multi-project scheduling and control: a process-based comparative study of the critical chain methodology and some alternatives</title>
  </titleInfo>
  <name type="personal">
    <namePart>Cohen, Izack</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Shtub, Avraham</namePart>
  </name>
  <name type="personal">
    <namePart>Mandelbaum, Avishai</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xu|</placeTerm>
    </place>
    <dateIssued>2004</dateIssued>
    <issuance>continuing</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">ng </languageTerm>
  </language>
  <physicalDescription>
    <extent>p.39-49.</extent>
  </physicalDescription>
  <abstract>Critical Chain (CC) is a popular project management technique in many multi-project organizations. it applies the Theory of Constraints (TOC) to offer a practical and easy method for planning, scheduling and control of multi-project systems. While some prior studies examined CC performance for single-project management, little attention has been given to its performance in a multi-project environment. In this paper, we examine the control mechanisms of CC and some alternatives. We demonstrate that, when CC is not enough to prevent projects' lateness, such alternatives may give rise to similar and sometimes better, possibly much better performance. - Reproduced.</abstract>
  <subject>
    <topic>Project management</topic>
  </subject>
  <relatedItem type="host">
    <name>
      <namePart>Project Management Journal</namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">180718</recordCreationDate>
  </recordInfo>
</mods>
