Project assumptions are a very real part of any project management cycle. It is fair to say that project managers assume that they will have the necessary budget and resources to deliver a completed project on time.
However, there are other types of assumptions that can quickly de-rail a project, such as technical specifications. These can, unfortunately, often be wrong, and that is why it is essential for a project manager to understand precisely what project assumptions are and how they can be identified at any stage of the project. Let’s take a look in more detail.
In project management, what are project assumptions?
The definition of project assumptions is “any factor relating to a project that is considered to be true, real, or certain — without any empirical proof or demonstration.” According to the PMI. In other words, they are the things you believe and assume to be true for the success of the project. At each stage of the project cycle, they will vary. Some of them may come true, some may not occur, and this means that all have inherent risks.
Why are project assumptions so important?
You can’t really plan a project without making assumptions; it’s impossible to do so. It is simply not achievable to see every variable of your project that might occur from the start to the finish, and for this reason you have to make assumptions. It is, however, essential to understand that they are assumptions and not facts and that they come with risks. They need to be identified during the planning process of your project because they can help you plan for possible risks that might impact your budget, timescales, or other aspects of the project.
Is there a connection between constraints, dependencies, risks and assumptions in your project?
For many who work in project management, the connections and distinctions surrounding project assumptions, constraints, dependencies and risks are not always very clear.
Constraints are those limitations that the project manager and team must work within. They usually include the following:
Dependencies are those activities or tasks that rely directly on another task or activity being completed or initiated. They often occur because of project constraints.
Risks are any unexpected events that can crop up and affect the project. They are not always negative, especially if assumptions have been identified appropriately and a plan created for their occurrence.
Managing project assumptions – best practices
You should follow best practices when it comes to managing your project assumptions:
Assess every political assumption
If it begins with “I think”, then consider it an assumption and add it to your list, then use this list to narrow down your most realistic assumptions. Everyone should be given the same sceptical consideration, and the consequences should be looked at together with how to mitigate them.
Integrate the assumptions
Once they have been identified and assessed through a future life-cycle for the project, they should be added to your project planning. This includes:
- All planned tasks
- Every point in the timeline of the project
- The budget
- The resources
- The members of the team
Maintain control
Assumptions may hinder the project, so be careful how you monitor their integration. If you don’t do this then you will not be able to activate your contingency plans.
Complete a post-project review
At the end of the project, review your assumptions and the process you had for evaluating them. This will offer you insights that will help with your next project. Ensure you include all the appropriate information required for a post-project review.
.
