Project complexity

Last updated

Project complexity is the property of a project which makes it difficult to understand, foresee, and keep under control its overall behavior, even when given reasonably complete information about the project system. [1] With a lens of systems thinking, project complexity can be defined as an intricate arrangement of the varied interrelated parts in which the elements can change and evolve constantly with an effect on the project objectives. [2] The identification of complex projects is specifically important to multi-project engineering environments. [3]

Contents

The domain was introduced by D. Baccarini in 1996. [4]

Types of complexity

Complexity can be:

Simple, complicated, complex, and really complex projects - based on the Cynefin framework. Simple, complicated, complex, and really complex projects.png
Simple, complicated, complex, and really complex projects - based on the Cynefin framework.

Based on the Cynefin framework developed by Dave Snowden, [6] complex projects can be classified as:

Project complexity has different components and sources, including the product (typically expressed in terms of structural or technological complexity); as well as the organization, its processes; the surrounding legal, ethical, and regulatory environment; stakeholder complexity and their (often conflicting) objectives; market complexity. Thus, when operating in a complex organization, or when developing a complex product, it is likely that the project itself will encounter phenomena related to dynamic complexity.

Project complexity management

The IT-PCM Project Complexity Management framework The IT-PCM Project Complexity Management framework.png
The IT-PCM Project Complexity Management framework

The IT-PCM project complexity management framework proposed by Stefan Morcov consists of 5 processes: [10]

  1. Plan IT project complexity management: the process of red-flagging complex projects, and deciding on management strategies and tools.
  2. Identify IT project complexity: the process of determining what elements of complexity characterize the project. It has as objective the detection, inventory, and description of the problem.
  3. Analyze IT project complexity: the process of analyzing and prioritizing the project complexity elements and characteristics. This step is concerned with understanding the problem.
  4. Plan IT project complexity response strategy: the process of developing options and actions to enhance and use Positive Complexity, and to reduce or avoid Negative Complexity. This step involves modeling and design of potential solutions.
  5. Monitor and Control IT project complexity: the process of implementing response strategies, monitoring, controlling, and evaluating the overall effectiveness. It is a continuous activity.

The typical response strategies are:

Positive, appropriate (requisite), and negative complexity

The Positive, Appropriate and Negative complexity model proposed by Stefan Morcov Positive complexity.png
The Positive, Appropriate and Negative complexity model proposed by Stefan Morcov

Similarly with the Law of requisite variety and The law of requisite complexity, project complexity is sometimes required in order for the project to reach its objectives, and sometimes it has beneficial outcomes. Based on the effects of complexity, Stefan Morcov proposed its classification as Positive, Appropriate, or Negative. [11] [9]

The concepts of Appropriate (requisite) and Positive Complexity are similar to opportunities in risk management, and to antifragility in vulnerability management as introduced by Nassim Nicholas Taleb.

See also

Related Research Articles

Complexity characterises the behaviour of a system or model whose components interact in multiple ways and follow local rules, leading to non-linearity, randomness, collective dynamics, hierarchy, and emergence.

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Risk management</span> Identification, evaluation and control of risks

Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.

Strategy is a general plan to achieve one or more long-term or overall goals under conditions of uncertainty. In the sense of the "art of the general", which included several subsets of skills including military tactics, siegecraft, logistics etc., the term came into use in the 6th century C.E. in Eastern Roman terminology, and was translated into Western vernacular languages only in the 18th century. From then until the 20th century, the word "strategy" came to denote "a comprehensive way to try to pursue political ends, including the threat or actual use of force, in a dialectic of wills" in a military conflict, in which both adversaries interact.

<span class="mw-page-title-main">Knowledge management</span> Process of creating, sharing, using and managing the knowledge and information of an organization

Knowledge management (KM) is the collection of methods relating to creating, sharing, using and managing the knowledge and information of an organization. It refers to a multidisciplinary approach to achieve organizational objectives by making the best use of knowledge.

Senior management, executive management, or upper management is an occupation at the highest level of management of an organization, performed by individuals who have the day-to-day tasks of managing the organization, sometimes a company or a corporation.

<span class="mw-page-title-main">SWOT analysis</span> Business planning and analysis technique

SWOT analysis is a strategic planning and strategic management technique used to help a person or organization identify Strengths, Weaknesses, Opportunities, and Threats related to business competition or project planning. It is sometimes called situational assessment or situational analysis. Additional acronyms using the same components include TOWS and WOTS-UP.

<span class="mw-page-title-main">Information management</span> Organisational activity concerning information lifecycle

Information management (IM) is the appropriate and optimized capture, storage, retrieval, and use of information. It may be personal information management or organizational. Information Management for organizations concerns a cycle of organizational activity: the acquisition of information from one or more sources, the custodianship and the distribution of that information to those who need it, and its ultimate disposal through archiving or deletion and extraction.

A complex adaptive system is a system that is complex in that it is a dynamic network of interactions, but the behavior of the ensemble may not be predictable according to the behavior of the components. It is adaptive in that the individual and collective behavior mutate and self-organize corresponding to the change-initiating micro-event or collection of events. It is a "complex macroscopic collection" of relatively "similar and partially connected micro-structures" formed in order to adapt to the changing environment and increase their survivability as a macro-structure. The Complex Adaptive Systems approach builds on replicator dynamics.

<span class="mw-page-title-main">Cynefin framework</span> Decision-making framework

The Cynefin framework is a conceptual framework used to aid decision-making. Created in 1999 by Dave Snowden when he worked for IBM Global Services, it has been described as a "sense-making device". Cynefin is a Welsh word for 'habitat'.

Complexity theory and organizations, also called complexity strategy or complex adaptive organizations, is the use of the study of complexity systems in the field of strategic management and organizational studies. It draws from research in the natural sciences that examines uncertainty and non-linearity. Complexity theory emphasizes interactions and the accompanying feedback loops that constantly change systems. While it proposes that systems are unpredictable, they are also constrained by order-generating rules.

<span class="mw-page-title-main">Dave Snowden</span> Welsh management consultant and researcher

David John Snowden is a Welsh management consultant and researcher in the field of knowledge management and the application of complexity science. Known for the development of the Cynefin framework, Snowden is the founder and chief scientific officer of The Cynefin Company, a Singapore-based management-consulting firm specialising in complexity and sensemaking.

In cybernetics, the term variety denotes the total number of distinguishable elements of a set, most often the set of states, inputs, or outputs of a finite-state machine or transformation, or the binary logarithm of the same quantity. Variety is used in cybernetics as an information theory that is easily related to deterministic finite automata, and less formally as a conceptual tool for thinking about organization, regulation, and stability. It is an early theory of complexity in automata, complex systems, and operations research.

Strategy implementation is the activities within a workplace or organisation designed to manage the activities associated with the delivery of a strategic plan.

Vulnerability management is the "cyclical practice of identifying, classifying, prioritizing, remediating, and mitigating" software vulnerabilities. Vulnerability management is integral to computer security and network security, and must not be confused with vulnerability assessment.

Robust decision-making (RDM) is an iterative decision analytics framework that aims to help identify potential robust strategies, characterize the vulnerabilities of such strategies, and evaluate the tradeoffs among them. RDM focuses on informing decisions under conditions of what is called "deep uncertainty", that is, conditions where the parties to a decision do not know or do not agree on the system models relating actions to consequences or the prior probability distributions for the key input parameters to those models.

Antifragility is a property of systems in which they increase in capability to thrive as a result of stressors, shocks, volatility, noise, mistakes, faults, attacks, or failures. The concept was developed by Nassim Nicholas Taleb in his book, Antifragile, and in technical papers. As Taleb explains in his book, antifragility is fundamentally different from the concepts of resiliency and robustness. The concept has been applied in risk analysis, physics, molecular biology, transportation planning, engineering, aerospace (NASA), and computer science.

Benefits realization management (BRM), also benefits management, benefits realisation or project benefits management, is a project management methodology, often visual, addressing how time and resources are invested into making desirable changes. BRM is used to manage the investment by organizations in procurement, projects, programmes and portfolios, and has been shown to increase project success across different countries and industries.

Opportunity management (OM) has been defined as "a process to identify business and community development opportunities that could be implemented to sustain or improve the local economy".

Roelf Johannes (Roel) Wieringa is a Dutch computer scientist who was a professor of Information Systems at the University of Twente, specialized in the "integration of formal and informal specification and design techniques".

References

  1. 1 2 Marle, Franck; Vidal, Ludovic‐Alexandre (2016). Managing Complex, High Risk Projects - A Guide to Basic and Advanced Project Management. London: Springer-Verlag.
  2. Bakhshi, Javad; Ireland, Vernon; Gorod, Alex (1 October 2016). "Clarifying the project complexity construct: Past, present and future". International Journal of Project Management. 34 (7): 1199–1213. doi:10.1016/j.ijproman.2016.06.002. S2CID   113426565.
  3. Vidal, Ludovic-Alexandre; Marle, Franck; Bocquet, Jean-Claude (2011). "Measuring project complexity using the Analytic Hierarchy Process" (PDF). International Journal of Project Management. 29 (6): 718–727. doi:10.1016/j.ijproman.2010.07.005. S2CID   111186583.
  4. Baccarini, David (1996). "The concept of project complexity—a review". International Journal of Project Management. 14 (4): 201–204. doi:10.1016/0263-7863(95)00093-3.
  5. Baccarini, D. (1996). "The concept of project complexity, a review". International Journal of Project Management. 14 (4): 201–204. doi:10.1016/0263-7863(95)00093-3.
  6. Snowden, David J.; Boone, Mary E. (2007). "A Leader's Framework for Decision Making". Harvard Business Review. 85 (11): 68–76.{{cite journal}}: CS1 maint: multiple names: authors list (link)
  7. Maurer, Maik (2017). Complexity Management in Engineering Design – a Primer. Berlin, Heidelberg: Springer.
  8. Kurtz, C.F.; Snowden, David J. (2003). "The new dynamics of strategy: Sense-making in a complex and complicated world". IBM Systems Journal. 42 (3): 462–483. doi:10.1147/sj.423.0462. S2CID   1571304.{{cite journal}}: CS1 maint: multiple names: authors list (link)
  9. 1 2 3 Morcov, Stefan (2021). Managing Positive and Negative Complexity: Design and Validation of an IT Project Complexity Management Framework. KU Leuven University. Available at https://lirias.kuleuven.be/retrieve/637007
  10. Morcov, Stefan; Pintelon, Liliane; Kusters, Rob J. (2021). "A Framework for IT Project Complexity Management". International Journal of Information Technology Project Management. IADIS IS 2021: 14th IADIS International Conference Information Systems: 61–68.
  11. Morcov, Stefan; Pintelon, Liliane; Kusters, Rob J. (2020). "IT Project Complexity Management Based on Sources and Effects: Positive, Appropriate and Negative" (PDF). Proceedings of the Romanian Academy - Series A. 21 (4): 329–336.