Academic
Publications
Managing multi-project environments through constant work-in-process

Managing multi-project environments through constant work-in-process,10.1016/S0263-7863(01)00058-8,International Journal of Project Management,S. Anav

Managing multi-project environments through constant work-in-process   (Citations: 20)
BibTex | RIS | RefWorks Download
This paper proposes new project control mechanisms that limit the number of active projects in multi-project environments. Incoming projects first enter a backlog list. Then, they are staggered into a network of inter-related resources in a way that maintains stable load on the system. The proposed mechanisms adapt the concept of constant work-in-process (CONWIP) that was proposed earlier in the context of production management. We report on an extensive set of simulations that were conducted with several types of projects in dynamic settings. We discuss possible preference rules for the backlog list and the resource queues within the system and demonstrate the superiority of a new rule whose objective is to achieve a dynamic balance of the loads of the various resources.
Journal: International Journal of Project Management - INT J PROJ MANAG , vol. 21, no. 1, pp. 9-18, 2003
Cumulative Annual
View Publication
The following links allow you to view full publications. These links are maintained by other sources not affiliated with Microsoft Academic Search.
    • ...Through in depth interviews and discussion the TP panel found out that the core conflict was "the quantity of open projects", which has been identified as the root cause of Undesirable Effects (UDEs) through rigorous cause-and-effect logic with Current Reality Tree (CRT) in company A. We quote Anavi-Isakow and Golany’s, “multi-projects run at the same time made bad multi-tasking and would jeopardize the project's schedule and ...

    Sheng-Hung Changet al. Limited number of open projects to shorten NPD schedule effectively

    • ...Through in depth interviews and discussion the TP panel found out that the core conflict was "the quantity of open projects", which has been identified as the root cause of Undesirable Effects (UDEs) through rigorous cause-and-effect logic with Current Reality Tree (CRT) in company A. We quote Anavi-Isakow and Golany’s, “multi-projects run at the same time made bad multi-tasking and would jeopardize the project's schedule and ...

    Sheng-Hung Changet al. Limited number of open projects to shorten NPD schedule effectively

    • ...Unfortunately, the research in this area has not converged to one solution or scheduling rule robust enough to hold in the general case [1]...

    José Alberto Araúzo Araúzoet al. Online Scheduling in Multi-project Environments: A Multi-agent Approac...

    • ...Papers addressing stochastic multi-project systems have started to appear only recently (e.g., Anavi-Isakow and Golany 2003; Cohen et al. 2005, Lee and Miler 2004)...
    • ...We demonstrate the approach through CONPIP (Anavi-Isakow and Golany 2003), a methodology that controls the load in the system by limiting the maximal number of projects in process...
    • ...We follow Anavi-Isakow and Golany (2003) who apply the pull principle in a dynamic, stochastic, multi-project system and show that it outperforms a push-based system (specifically, the average total throughput time of a project—from its arrival into the system until its departure—is lower)...
    • ...The COnstant Number of Projects In Process (CONPIP) model, developed by Anavi-Isakow and Golany (2003), limits the number of projects in the system to a fixed number (NPIP)...

    Izack Cohenet al. Resource allocation in stochastic, finite-capacity, multi-project syst...

Sort by: