Last updated on February 2, 2016
Do you know what the difference between Project Constraints, Assumptions and Dependencies is?
I have written a small series of posts to describe Project Constraints, Project Assumptions and Project Dependencies. Although these terms look simple but sometimes they are confusing in practice. This post is written to describe Project Constraints. You should be able to understand the difference between these terms after reading all 3 posts. These three terms have immense utility in Project Management if they are used appropriately.
What is a Project Constraint?
According to PMBOK® Guide 5th Edition, Project Constraint is “A limiting factor that affects the execution of a project, program, portfolio or a process”.
Another definition could be “Project Constraints are restrictions imposed by Stakeholders or Environment that limits Project Team’s options”.
You can also look at Max Wideman’s Glossary for the definition of Project Constraints.
According to PMBOK® Guide 5th Edition, Project Management involves balancing the Competing Project Constraints. These include, but are not limited to:
Project Constraints simply mean that, Project Teams always work under some limitations and restrictions. Project Management involves balancing these limitations for successful completion of Project. In ideal conditions (when there are no Project Constraints), a Project Manager may have unlimited options but in practice the Project Manager must find ways to work within known limitations. Project Manager, along with the Team, creates a Project Plan while considering and balancing known Project Constraints.