Project complexity: Difference between revisions

Revision as of 18:29, 14 February 2022

Revision as of 10:49, 17 March 2022

Line 9:

* '''Structural complexity''' (also known as detail complexity, or complicatedness), i.e. consisting of many varied interrelated parts.<ref>{{Cite journal|last=Baccarini|first=D.|date=1996|title=The concept of project complexity, a review|journal=International Journal of Project Management|language=en|volume=14|issue=4|pages=201–204|doi=10.1016/0263-7863(95)00093-3}}</ref> It is typically expressed in terms of size, variety, and interdependence of project components, and described by technological and organizational factors.

* '''Dynamic complexity''', which refers to phenomena, characteristics, and manifestations such as ambiguity, uncertainty, propagation, emergence, and chaos.<ref name="Springer-Verlag" />

[[File:Simple,_complicated,_complex,_and_really_complex_projects.png|thumb|Simple, complicated, complex, and really complex projects - based on the [[Cynefin framework|Cynefin]] framework.]]

Based on the [[Cynefin framework]] developed by [[Dave Snowden]],<ref>{{Cite journal|last=Snowden, David J.; Boone, Mary E.|date=2007|title=A Leader's Framework for Decision Making|url=https://hbr.org/2007/11/a-leaders-framework-for-decision-making|journal=Harvard Business Review|language=en|volume=85|issue=11|pages=68–76}}</ref> complex projects can be classified as:

* '''Simple''' (or clear, obvious, known) projects, systems, or contexts. These are characterized by known knowns, stability, clear cause-and-effect relationships. They can be solved with standard operating procedures and best practices.