Cone of Uncertainty
Agile Product

Cone of Uncertainty

Cone of Uncertainty reflects the variability of the project through its lifetime. The variability is decreasing as more is known.
Read more
Get PDF
Tags
Agile cone of uncertainty cone of uncertainty agile cone of uncertainty hurricane cone of uncertainty scrum estimation hurricane cone of uncertainty image Infographic Poster Product Product development Scrum the cone of uncertainty
Article

Cone of Uncertainty


Uncertainty is very certain.

At the start of the project, there are a lot of variables that need to be taken into account. All projects have different requirements, different priorities, different people working, or different technologies. These are the reasons why the variables coming into the project are not clear at the beginning of a project. The variability of these factors is reflected in the project variability. The result is that estimates must include the variability. After the project starts and more is known, the variability is decreasing. This phenomenon is called the “Cone of Uncertainty”. A significant narrowing of the Cone occurs during the first 20-30%.

Cone of uncertainty.

Estimation tips

  1. Make a visible list of risks
  2. Inspect and update risks and estimates regularly
  3. Eliminate improbable options as the project progresses
  4. Add a pad to your estimates
  5. Compare and size the project relative to other projects

Resources
construx.com wikipedia.org scrumexpert.com agilenutshell.com techagileleaders.com medium.com

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.