Alternative name


An assumption can be described as an assured statement pertaining to the eventual outcome of an event in the future. This could be as a result of uncertainty. According to the Oxford dictionary, an assumption is a statement or fact that an event will happen even without proof. In planning of a project, a number of assumptions are made at the initial phase of a project, it is then based on this assumptions that risk could be identified and the necessary steps taken to avoid them are implemented. In life, changes in circumstances can result in plans being in tatters. For example, it is assumed by a farmer that there will be more than enough sunlight for his crops to grow in certain seasons. The world changes every day and things might not necessary work out the way we assumed.

Agile values

Communication-: Communication is an integral aspect of stakeholder management in projects because it ensures that clashes are avoided. Requirements are better communicated to the project team to ensure that whatever is been developed is achieved. Therefore, communication between project team and stakeholder is of vital importance

Agile principles

Open Information--unclear information could cause ambiguity to occur in a project team. Ambiguity is better managed through the employment of open information because it enables cooperation among team members and aids in the avoidance of conflicts that regularly occur as a result of limited information (Orville et al, 1975). Information sharing boost mutual relationship among staff members and improves communication to ensure that any problem that may arise can be easily dealt with so that the expectation of stakeholders are met.

Agile practices


Facts should be the basis of assumption based on the evidence readily available at the time. Increase in uncertainty brings about an increase in the assumptions made under a given circumstance. Assumption basically entails some level of risk and could be documented in the risk log. During the initiation phase of project development, there is usually a reasonable amount of assumptions. It is essential to monitor all assumptions to ensure that their impact on the project development is limited otherwise contingency plans should be developed to tackle the issues that may arise from that assumption. Assumptions based on estimation are a regular occurrence in projects and should be properly documented. In the development of software, assumptions are made about the operational environment. This assumptions are built into the system but not necessarily recorded (Lehman, 1989). Assumptions are limitless and could fail at any given time resulting in software failure. In a world rapidly becoming software dependent, the impact of a failure based on assumption could be critical (Lehman, 1989).

Links from this KA to other KAs

Project Risk Management:Assumptions management is related to risk management because they work around uncertainties with the aim of preventing the occurrence of a risk event that could cause a project to fail.
Ambiguity Management: Assumptions management is related to ambiguity as they are both aimed at eliminating uncertainties in a project environment


Agile Alliance and Institute Agile. (2011). Guide to Agile Practices. Available: [Accessed: 19 February, 2015]

Lehman. M (1989) “Uncertainty in computer application and its control through the engineering of software”, Journal of Software Maintenance: Research and Practice, John Wiley & Sons, Ltd, pp. 3-27

Orville C, Walker, Jr, Gilbert A, Churchill, Jr & Neil M (1975) Organizational Determinants of the Industrial Salesman’s Role Conflict and Ambiguity Journal of Marketing 39 (1) pp. 32-39 [Online] Available: [Accessed: 6th April 2013]

External links

Assumption management
Assumption and constraints in project management

Read in another language