{"id":19294,"date":"2024-10-27T09:21:38","date_gmt":"2024-10-27T07:21:38","guid":{"rendered":"https:\/\/pmdoc.ua\/uncertainty-in-project-management\/"},"modified":"2024-10-27T15:43:26","modified_gmt":"2024-10-27T13:43:26","slug":"uncertainty-in-project-management","status":"publish","type":"post","link":"https:\/\/pmdoc.ua\/en\/uncertainty-in-project-management\/","title":{"rendered":"Uncertainty in Project Management"},"content":{"rendered":"\n

I have long noticed that uncertainty<\/strong> has the greatest impact on my projects and the implementation of project management systems<\/a>. This ‘uncertainty’ is essentially the inverse measure of knowledge and understanding. If we know everything, have statistics, experience, and established processes, then project management isn\u2019t needed\u2014simple work administration would suffice. On the other hand, if the initiative we are undertaking is quite unique, and we lack detailed knowledge and sufficient understanding of how to proceed\u2014meaning we are in a state of uncertainty\u2014we begin using project management methods and tools to reduce this uncertainty.<\/p>\n\n\n\n

For example, what is a Gantt Chart, essentially? Sometimes it is called a ‘schedule’ or ‘timetable,’ but a ‘timetable’ is for things like educational classes or transportation schedules, where there is a degree of certainty.<\/p>\n\n\n\n

A Gantt Chart, on the other hand, is just a model of the future. It can be well-developed, based on previous experience or analogous projects, but it will always remain a model because there is always the potential for something to go wrong\u2014something we didn\u2019t anticipate or an unexpected event that might occur.<\/p>\n\n\n\n

\"PERT<\/figure>\n\n\n\n

The two main approaches today\u2014predictive (waterfall) and adaptive (agile)\u2014primarily differ in how they handle uncertainty. Predictive approaches reduce uncertainty ‘theoretically’ through planning and modeling, while adaptive approaches address it ’empirically’ through short cycles of trials and feedback. However, if we introduce progressive elaboration into the predictive approach and high-level planning with a roadmap into the adaptive approach, the differences between these approaches nearly disappear.<\/p>\n\n\n\n

The first deliberate approach to reducing uncertainty in creating something new and large-scale was PERT. In essence, PERT was humanity’s first attempt to address uncertainty in projects. While Gantt charts, Adamiecki’s harmonograms, Fayol’s management functions, and Taylor’s scientific management theories were important contributions to improving general management, PERT’s ideas, approaches, and tools specifically reduced uncertainty in project management to such an extent that we still use them today (greetings to everyone who still thinks that PERT is a three-point estimate and are unaware of where the WBS originated<\/em>).<\/p>\n\n\n\n

It is clear that\u00a0even with the advent of PERT, uncertainty did not disappear completely. In fact, as the pace of change increased, uncertainty contributed to the development of agile and other adaptive approaches.<\/p>\n\n\n\n

However, it seems that the developers of PERT addressed the uncertainty of their time so virtuously that even PMI did not pay attention to this problem for as many as three versions of the PMBOK. These first editions mention uncertainty in connection with uniqueness, risks, and PERT itself. It wasn\u2019t until the fourth edition of the PMBOK that this figure appeared:<\/p>\n\n\n\n

\"Figure<\/figure>\n\n\n\n

Both the fourth and fifth editions of the PMBOK view uncertainty primarily through the lens of risks. It wasn\u2019t until the release of Navigating Complexity: A Practice Guide<\/a> in 2014 (50 years after the introduction of PERT<\/em>) that PMI began to give sufficient attention to uncertainty. The sixth edition of the PMBOK already includes substantial information on the topic, and by the seventh edition, a separate domain\u2014’Uncertainty<\/strong>‘\u2014was introduced.<\/p>\n\n\n\n

However, we are still there\u2014uncertainty related to projects remains as it was.<\/p>\n\n\n\n

I believe that if we could fully address uncertainty, project management would either no longer be necessary<\/strong> or would transform into operational management and business administration.<\/p>\n\n\n\n

This may sound categorical, but I assert<\/strong> that all<\/strong> processes, tools, and artifacts of project initiation and planning are focused on one thing<\/strong>: combating uncertainty. Yet they do it poorly, so in the processes of execution and control, we continue working to reduce uncertainty. The only closing processes bring a partial resolution to this issue, but not for all aspects of the project’s outcome. For example, the true value for the project can often only be measured over time.<\/p>\n\n\n\n

Now, the question:<\/h2>\n\n\n\n

PMI defines ‘uncertainty<\/em>‘ as ‘a lack of understanding and awareness of issues, events, paths to follow, or solutions to pursue<\/em>.’ It also uses terms like ‘degree of uncertainty,’ ‘measure of uncertainty,’ ‘amount of uncertainty,’ and ‘value of uncertainty,’ without offering any clear indication of how uncertainty can actually be measured. So<\/span>:<\/p>\n\n\n\n

    \n
  1. How exactly can uncertainty be measured?<\/strong><\/li>\n\n\n\n
  2. What could be the unit of measurement for uncertainty?<\/strong><\/li>\n<\/ol>\n\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    Uncertainty is the inverse measure of knowledge and understanding. If we know everything, have statistics, experience, and established processes, then project management isn\u2019t needed…<\/p>\n","protected":false},"author":1,"featured_media":19283,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[366],"tags":[954,542,744,955],"class_list":["post-19294","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles","tag-pert","tag-pmbok","tag-project-management","tag-uncertainty"],"_links":{"self":[{"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/posts\/19294","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/comments?post=19294"}],"version-history":[{"count":2,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/posts\/19294\/revisions"}],"predecessor-version":[{"id":19299,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/posts\/19294\/revisions\/19299"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/media\/19283"}],"wp:attachment":[{"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/media?parent=19294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/categories?post=19294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pmdoc.ua\/en\/wp-json\/wp\/v2\/tags?post=19294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}