Assumptions and constraints in a project :
Assumptions and constraints are part of the projects. Its very important a PM or a BA needs to understand the assumptions and constraints of their respective projects as it impacts the project as whole if not given high importance. So, lets understand , how to identify and manage them. There are three things to look at i.e, assumptions, and again constraints are divided into two and they are business constraints and technical constraints
Constraints are nothing but fixed conditions or limitations on what you can do.. For example you may want to travel @100kmph in the city but that’s not possible as speed limits is the constraint here. Meaning here you need to understand you cannot change these constraints instead you need to understand and manage accordingly.
Assumptions : Assumptions are factors that we believe to be true, although these factors are not confirmed to be true. Assumptions add risk to a project since it is possible that they will turn out to be false. Assumptions can impact any part of your project life cycle and resulting solution implementation, so it is important to document and analyze them.
Business constraints : Business constraints usually limit the solution based upon the current organizational state. It focuses on the available time, money and resources for a project. Mostly business constraints include budget and time restrictions, resource limitations, and resource skill limitations. For example, your project’s business case may contain assumptions about realizing the business benefits for your project. Any assumptions about a specific business benefit should be documented and linked to the requirements that will deliver those benefits. This may introduce additional risk into the premises contained in the business case, since it is possible that the assumptions you are assuming to be true may not be true in the end.
Technical constraints : Technical constraints often focus on architecture decisions that limit your solution design. They tend to be inflexible and unchanging, and can have an impact on your solution implementation. They include areas such as development languages, hardware, other infrastructure, and software that must be used for your project.
Note: Remember, any project stakeholder may be involved with identifying and defining the assumptions and constraints for your project, so keep your ears open! The project team should use these assumptions and constraints to identify potential risks that may impact project implementation and delivery or have a negative impact on end-user expectations of the resulting solution. It is essential to keep a handle on the assumptions and constraints that are part of your project.