Project complexity

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. 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. The identification of complex projects is specifically important to multi-project engineering environments.

The domain was introduced by D. Baccarini in 1996.

Types of complexity

Complexity can be:

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

Based on the Cynefin framework developed by Dave Snowden, 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 proposed by Stefan Morcov consists of 5 processes:

  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

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.

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