Project Assumptions: A Quick Guide

Project Assumptions: A Quick Guide

Project assumptions are essential for planning a project. They are used to define a factor that is true, real or certain, even if there isn't proof. They are important because they open the door to the project and its planning. Analyzing assumptions is part of project risk management, and if they are proven wrong, they must be identified, tracked and managed throughout the life cycle of the project. A project assumption log is a key piece of data for creating and reviewing the project plan.

A project manager must make an assumption log during the initiation phase of a project to inform the writing of the project charter. It should include the date, category, name and description of the assumption, impact, rate of uncertainty, assign an owner, define a plan of action to mitigate the impact, set date for next review, and note the status of the assumption. Project managers are able to make assumptions about the project due to experience, research, and expert advice. There are six constraints in projects: scope, quality, schedule, budget, resources, and risk. Business constraints are high-level issues that depend on the organization, while technical constraints limit design choices. Assumptions tend to be good for the project, while constraints are not.