From the Editor
Authors: Hans Georg Gemünden
Year: 2013

© 2013 by the Project Management Institute Published online in Wiley Online Library (wileyonlinelibrary.com). DOI: 10.1002/pmj.21383 First, I want to share some very good news with the project management research community and all our readers interested in project management research. The deadline for the submission of papers to the PMI research conference has been prolongated to 13 January 2014. The PMI® Research and Education Conference, “Standing on the Shoulders of Giants: In Search of Theory and Evidence” will be held on 27–29 July 2014 in Portland, Oregon, USA. We welcome conceptual, empirical, or theoretical work using project, program, or portfolio management as the subject or context of the research. PMI also solicits papers and symposia on project management education; doctoral students are encouraged to submit their work to the pre-conference doctoral colloquium. For submission guidelines and instructions, please contact PMI.org/REC2014submit. Conference registration is scheduled to open March 2014 and details can be found on PMI.org/REC2014. The December issue of Project Management Journal® offers a rich variety of articles, each of which delivers a significant contribution to theory building in project organizing and new empirical findings with a high value of theory and practice. The first paper by Dietrich, Kujala, and Artto addresses a fundamental organizational design question in project management: How should the interdependencies between different teams in a multi-team project be managed? There are many different coordination mechanisms, but each of them has its advantages and drawbacks and they can be combined in different ways, which differ in terms of coherence and potential synergies. The organizational design reflections stated in this article can also be used for the management of programs consisting of an array of different projects or for the management of a project portfolio in which the management of interdependencies between projects is also a critical challenge. The management of interdependencies between projects is an issue that has been neglected in multi-project management. Very often the interdependence is restricted to resource conflicts between projects and the solution is to identify the bottleneck resources and the projects that conflict with one bottleneck resource. The solution to this problem is often a muddling-through approach that delivers an immediate solution, yet doesn’t acknowledge that typically there are too many projects occurring at the same time, and that an organization usually experiences a number of bottlenecks simultaneously. This bottleneck obstacle makes it difficult to assess the consequences of measures that have been taken to repair an immediate problem—a problem that may only be a symptom of a much larger and obscure problem. In addition, there are many kinds of different interdependencies between projects that have not been addressed systematically and simultaneously. Markowitz’s pioneering work showed that the risk of a portfolio of projects can be reduced if the project portfolio mixture combines projects, which in sum show a smaller covariance of cash-flow. Thus, managing risk interdependencies between financial investments, which could have been projects, in such a way that the overall risk of a portfolio of financial investments, which could have been projects, is reduced, has been an essential element of designing portfolios since long. Organizational design theory made the claim that the kinds of interdependencies matter; in other words, for pooled, sequential, or reciprocal interdependencies, different kinds of organizational coordination instruments—or more precisely, different kinds of coherent mixes of coordination instruments—should be used. Regarding project portfolio management, pooled interdependencies among scarce (human) resources during the development stage of a new product, process, or service, have been the focus of interest. But pooled interdependencies are not restricted to human resources in the development process or to financial resources in a more aggregated view. If potential users of a project can only cope with a limited amount of new products or product releases that are delivered to them, this creates a new, thus far, often neglected type of bottleneck. The ability and willingness of users or intermediaries may also create bottlenecks and thus “pooled” interdependencies. Transfer prices or prioritization systems have been proposed to solve the internal resource coordination problem, but do they also apply to the customer acceptance bottleneck problem? Taking a marketing perspective or a purchasing perspective, additional interdependence aspects have to be considered. If two projects share the same customer as a recipient, or the same supplier as a source, then these two projects need to be coordinated. (This may pertain to the following questions: When should which project be done? What should it deliver to other projects serving the same client?) Or: Do resource From the Editor