Pooled, Sequential & Reciprocal dependence

Motivation An article on this topic already exists on the wiki. However, I believe I can improve/supplement this article on a number of points: 1) Elaborate on the application potential of the different types of dependencies. 2) Supplement the original theory, from James D. Thomson’s Organizations in Action, with today’s perspective on it (how the theory has evolved). 3) Take the theory from its original focus on project management and discuss its application potential on program and portfolio management levels. 4) Describe dependencies’ ability to work as a Risk Management tool

The topic is highly relevant to our case, and I hope this can be used to write a better article as well as prove useful on the case work.

Abstract (Draft)

A project consists of a series of tasks that need to be executed in order to complete it. The way these tasks are arranged in relation to each other will come down to their dependence. According to James D. Thompson, task dependence can be distinguished into three types: Pooled, Sequential and Reciprocal. For a Project Manager dependencies can be a powerful tool in managing the complexity of a project. Using dependencies to characterise tasks in a project will help to determine the sequence of which tasks should be completed in order to optimise time use, resources, workers, etc. A way dependencies are not used much yet is on the levels above project management, namely program and portfolio management. Here, dependencies could prove useful in terms of optimising efficiency in a program or portfolio setting, spanning across several projects. All this will be explored in greater detail and described in the article.

Big Idea

REMOVE:: Introduction to J. D. Thompson’s “Organizations in Action”, and the origin of three dependency types: Pooled, Sequential and Reciprocal.

Complexity

A project consists of a series of interdependent tasks. These need to be completed in a certain manner which is determined by each task’s link(s) to other tasks. In this way, a project can be seen as a dynamic system where factors such as the number of tasks, their interconnectivity, uncertainty and ambiguity makes up a projects degree of complexity. INSERT REFERENCE A Project Managers ability to manage this complexity, in any variable shape or form it might take, is crucial for a projects chance of success. Tools that help deal with the different factors of complexity are therefore important for Project Managers to know about.

One such tool

Purpose

• Improve resource management
• Improve resource efficiency
• Mitigate uncertainties (time management)
• Mitigate risk (Less uncertainty)

Application

Project level

OBS: The following sections are placeholders - There appears to be a valid argument for distinguishing between applying dependencies on the 3P’s of management, but whether these are different enough to justify their own header is not yet clear.

Applying dependencies in other settings

Looking at how to apply the theory on a project, program and portfolio level in various types of companies.

Limitations

A look into how the field have developed since the original introduction in 1967. How the old theory falls short (Lack of depth and distinguish between the three original types of dependency)

Annotated Bibliography

Bilgin, G. et al. (2017) “Handling project dependencies in portfolio management,” Procedia Computer Science, 121, pp. 356–363. Available at: https://doi.org/10.1016/j.procs.2017.11.048. - Article on applying dependency management on a cross-project portfolio level

Knotten, V. et al. (2015) “Design management in the building process - A review of current literature,” Procedia Economics and Finance, 21, pp. 120–127. Available at: https://doi.org/10.1016/s2212-5671(15)00158-6. - Article looking at the current practices of using dependencies

Kwan, T.W. and Leung, H.K.N. (2011) “A risk management methodology for Project Risk Dependencies,” IEEE Transactions on Software Engineering, 37(5), pp. 635–648. Available at: https://doi.org/10.1109/tse.2010.108. - Article on identifying dependencies between risks in order to create better risk management

Lemak, D.J. and Reed, R. (2000) “An application of Thompson's typology to TQM in service firms,” Journal of Quality Management, 5(1), pp. 67–83. Available at: https://doi.org/10.1016/s1084-8568(00)00013-4. - Article on how to apply the theory of Thompson, J.D. in an untypical setting. Here a service firm

Lundberg, C.C. and Thompson, J.D. (1967) “Organizations in action.,” Administrative Science Quarterly, 12(2), p. 339. Available at: https://doi.org/10.2307/2391555. - The original introduction of the Pooled, Sequential & Reciprocal dependence theory

Tsvetkova, A., Eriksson, K., Levitt, R. E., & Wikstrom, K. (2019). Workflow interdependence analysis of projects in business ecosystems. The Engineering Project Organization Journal, 8, 1-18. - Application of the Thompson, J.D. theory in a different setting

Volkoff, O., Strong, D.M. and Elmes, M.B. (2005) “Understanding enterprise systems-enabled integration,” European Journal of Information Systems, 14(2), pp. 110–120. Available at: https://doi.org/10.1057/palgrave.ejis.3000528. - Article on using Thompson, J.D.’s dependency theory to understand and optimise company work processes