Subject: | [AISWorld] AMCIS 2013 CFP: IT Project Management |
---|---|
Date: | Fri, 28 Dec 2012 12:31:30 -0500 (EST) |
From: | Michael A Chilton <mchilton@ksu.edu> |
Reply-To: | Michael A. Chilton <mchilton@ksu.edu> |
To: | aisworld@lists.aisnet.org |
Call for Papers
One factor that affects all project management endeavors is the constraint imposed by limited resources. Extensive research in the past 10 to 15 years has been devoted to this problem and a plethora of software tools are available with features devoted to resource leveling, but scheduling projects under the condition of limited resources is still a huge problem. Scholars have devise algorithms and heuristics to assist the problem of scheduling under the constraint of limited resources, but many of these studies apply only to simple projects that are restricted by a number of simplifying assumptions. PERT/CPM techniques identify a critical pathâa set of tasks that if any single task is delayed will delay the entire project. But is the critical path worthy assumes that unlimited resources are available. And so, is it worthy of the attention it has been given? According to Herroelen and Leus (2005, p. 102), perhaps not:
âThis âcritical pathâ notion indeed invites project managers to become trapped in the erroneous belief that the critical path determines the duration of the project, the misconception that the critical path activities are always the ones that require the most attention during planning and that effective project control implies that management should invariably concentrate their control efforts especially on the critical path activities during project execution.â
To address this problem, the critical chain was developed, based on the Theory of Constraints, which states that a system must have at least one constraint affecting its throughput. Still falling short of expectations, especially where determination of slack is concerned, the critical sequence was developed to help identify those activities that were critical and calculate exactly which activities had slack and how much.
Research is needed in this area to find solutions that practitioners can use to better estimate and (hopefully) to shorten project duration, and to make changes along the way as needs and the availability of resources change during the life of a project. This is even more important given that most IT shops are involved in several projects simultaneously.
We solicit papers that deal with these and other topics of project management as they relate to resource leveling, assignment and scheduling. The focus of this mini-track is on the allocation and scheduling of resources to tasks within a multi-project IT shop.
Reference:
Herroelen, W. & Leus, R. (2005). âIdentification and illumination of popular misconceptions about project scheduling and time buffering in a resource-constrained environment,â Journal of the Operations Research Society, 56, pp. 102-109.