Content deleted Content added
Bot: Removing c:File:Simple, complicated, complex, and really complex projects.png , deleted by Túrelio (Copyright violation: 2021 book source). Tag: Reverted |
m Open access bot: url-access updated in citation with #oabot. |
||
| (8 intermediate revisions by 6 users not shown) | |||
Line 1:
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.<ref name="Springer-Verlag">{{Cite book|last1=Marle|first1=Franck|title=Managing Complex, High Risk Projects - A Guide to Basic and Advanced Project Management|last2=Vidal|first2=Ludovic‐Alexandre|date=2016|publisher=Springer-Verlag|___location=London}}</ref>
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.<ref>{{cite journal |last1=Bakhshi |first1=Javad |last2=Ireland |first2=Vernon |last3=Gorod |first3=Alex |title=Clarifying the project complexity construct: Past, present and future |journal=International Journal of Project Management |date=1 October 2016 |volume=34 |issue=7 |pages=1199–1213 |doi=10.1016/j.ijproman.2016.06.002 |s2cid=113426565 }}</ref> The identification of complex projects is specifically important to multi-project engineering environments.<ref>{{Cite journal|last1=Vidal|first1=Ludovic-Alexandre|last2=Marle|first2=Franck|last3=Bocquet|first3=Jean-Claude|date=2011|title=Measuring project complexity using the Analytic Hierarchy Process|url=https://hal.archives-ouvertes.fr/hal-01215358/file/Vidal%20et%20al%20-%202011%20-%20IJPM%20-%20Measuring%20project%20complexity%20using%20the%20AHP.pdf|journal=International Journal of Project Management|language=en|volume=29|issue=6|pages=718–727|doi=10.1016/j.ijproman.2010.07.005|s2cid=111186583 }}</ref>
The ___domain was introduced by D. Baccarini in 1996.<ref>{{Cite journal|last=Baccarini|first=David|date=1996|title=The concept of project complexity—a review|url=https://linkinghub.elsevier.com/retrieve/pii/0263786395000933|journal=International Journal of Project Management|language=en|volume=14|issue=4|pages=201–204|doi=10.1016/0263-7863(95)00093-3|url-access=subscription}}</ref>
== Types of complexity ==
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.
Line 18 ⟶ 20:
== Project complexity management ==
[[File:The IT-PCM Project Complexity Management framework.png|thumb|The IT-PCM Project Complexity Management framework]]
The IT-PCM project complexity management framework proposed by Stefan Morcov consists of 5 processes:<ref>{{Cite journal|
# '''Plan IT project complexity management:''' the process of red-flagging complex projects, and deciding on management strategies and tools.
Line 48 ⟶ 50:
* [[Antifragility]]
{{DEFAULTSORT:Project Management}}
[[Category:Project management
== References ==
Line 54 ⟶ 56:
[[Category:Complex systems theory]]
[[Category:Risk management]]
| |||
