Assumptions
Definition Assumption: Something taken for granted or accepted as true without proof; a supposition, ie. an opinion or belief without sufficient evidence. Assumptions are circumstances and events that need to occur for the project to be successful, but are outside the total control of the project team. Assumptions are accepted as true, often without proof or demonstration. Constraints are things that might restrict, limit, or regulate the project. Generally constraints are outside the total control of the project team. Why is This Important? Assumptions that prove to be incorrect can have a significant impact on a project. It is important that project participants, stakeholders and executives understand and agree with the assumptions before the project begins. This way, it is more likely that an incorrect assumption will be detected before it can impact the project. All projects have constraints, and these need to be defined from the outset. If the project leader understands the limitations under which a project must be conducted, including the project environment or parameters (timeframes and deadlines, funding, skill levels, resource availability, etc.), they will do a better job of developing the project plan. Early project risk analysis often uses the assumptions and constraints as a starting point. This provides a foundation for building mitigation strategies for the most significant assumptions that, if proven incorrect, could seriously impact the project. Likewise, it provides for the evaluation of constraints and the opportunity to manage them to positively impact the project or prevent a negative impact. Steps 1. Briefly and clearly describe any project assumptions related to business, technology, resources, scope, expectations, or schedules. List the project assumptions based on the current knowledge today. 2. Describe the principal constraints