Cone of Uncertainty

In project management, the Cone of Uncertainty However, " the cone of probability " describes the best forecast concerning the future path of a strong weather event considering all of the atmospheric conditions available to the forecasters at the time. Thus - Cone of Probability. evolution of the amount of best case uncertainty during a project (Construx n.d.). At the beginning of a project, comparatively little is known about the product or work results, and so estimates are subject to large uncertainty. As more research and development is done, more information is learned about the project, and the uncertainty then tends to decrease, reaching 0% when all residual risk has been terminated or transferred. This usually happens by the end of the project i.e. by transferring the responsibilities to a separate maintenance group.

The term Cone of Uncertainty is used in software development where the technical and business environments change very rapidly. However, the concept, under different names, is a well-established basic principle of cost engineering. Most environments change so slowly that they can be considered static for the duration of a typical project, and traditional project management methods therefore focus on achieving a full understanding of the environment through careful analysis and planning. Well before any significant investments are made, the uncertainty is reduced to a level where the risk can be carried comfortably. In this kind of environment the uncertainty level decreases rapidly in the beginning and the cone shape is less obvious. The software business however is very volatile and there is an external pressure to decrease the uncertainty level over time. The project must actively and continuously work to reduce the uncertainty level.

The Cone of Uncertainty is narrowed both by research and by decisions that remove the sources of variability from the project. These decisions are about scope, what is included and not included in the project. If these decisions change later in the project then the cone will widen.

Original research for engineering and construction in the chemical industry demonstrated that actual final costs often exceeded the earliest "base" estimate by as much as 100% (or underran by as much as 50%; Bauman 1958). Research in the software industry on the Cone of Uncertainty stated that in the beginning of the project life cycle (i.e. before gathering of requirements) estimates have in general an uncertainty of factor 4 on both the high side and the low side (Boehm 1981). This means that the actual effort or scope can be 4 times or 1/4 of the first estimates. This uncertainty tends to decrease over the course of a project, although that decrease is not guaranteed (McConnell 2006, p. 38).

Applications

One way to account for the Cone of Uncertainty in the project estimate is to first determine a 'most likely' single-point estimate and then calculate the high-low range using predefined multipliers (dependent on the level of uncertainty at that time). This can be done with formulas applied to spreadsheets, or by using a project management tool that allows the task owner to enter a low/high ranged estimate and will then create a schedule that will include this level of uncertainty.

A projected three- and five-day path of Hurricane Irene, here downgraded to a tropical storm

The Cone of Uncertainty is also used extensively as a graphic in hurricane forecasting, where its most iconic usage is more formally known as the NHC Track Forecast Cone (NHC n.d.), and more colloquially known as the Error Cone, Cone of Probability, CONUS, or the Cone of Death. (Note that the usage in hurricane forecasting is essentially the opposite of the usage in software development. In software development, the uncertainty surrounds the current state of the project, and in the future the uncertainty decreases, whereas in hurricane forecasting the current location of the storm is certain, and the future path of the storm becomes increasingly uncertain) (Hennen 2011). Over the past decade, storms have traveled within their projected areas two-thirds of the time (CRED 2007), and the cones themselves have shrunk due to improvements in methodology. The NHC first began in-house five-day projections in 2001, and began issuing such to the public in 2003. It is currently working in-house on seven-day forecasts, but the resultant Cone of Uncertainty is so large that the possible benefits for disaster management are problematic (Kleinberg 2011).

History

The original conceptual basis of the Cone of Uncertainty was developed for engineering and construction in the chemical industry by the founders of the American Association of Cost Engineers (now AACE International). They published a proposed standard estimate type classification system with uncertainty ranges in 1958 (Gorey 1958) and presented "cone" illustrations in the industry literature at that time (Bauman 1958). In the software field, the concept was picked up by Barry Boehm (Boehm 1981, p. 311). Boehm referred to the concept as the "Funnel Curve" (Stutzke 2005, p. 10). Boehm's initial quantification of the effects of the Funnel Curve were subjective (Boehm 1981, p. 311). Later work by Boehm and his colleagues at USC applied data from a set of software projects from the U.S. Air Force and other sources to validate the model. The basic model was further validated based on work at NASA's Software Engineering Lab (NASA 1990 p. 3-2).

The first time the name "Cone of Uncertainty" was used to describe this concept was in Software Project Survival Guide (McConnell 1997).

Implication
  • Estimates (e.g. on duration, costs or quality) are inherently very vague at the beginning of a project
  • Estimates and project plans based on estimations need to be redone on a regular basis
  • Uncertainties can be built into estimates and should be visible in project plans
  • Assumptions that later prove to be mistakes are major factors in uncertainty
gollark: Nope. No good text editor actually works like that.
gollark: I'm inferring.
gollark: Unless you've written more code than I assumed, it isn't actually doing that, it's rewriting the file with the entire array each time.
gollark: 642.
gollark: You're saving an object or array or something to a JSON file when you're updating some data, right?

See also

References

Further reading
  • Bossavit, Laurent (2013), The Leprechauns of Software Engineering.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.