ITtoolkit Article Collection


Using Assumptions and Constraints for Realistic Project Planning


Read more in the full article below.

Few projects begin with absolute certainty. If absolute certainty was an "absolute" requirement, few projects would ever get off the ground. That's why "assumptions" and "constraints" are so important, used as key defining factors to ensure timely, realistic project results. Read on to learn more.

As projects are planned and executed, some facts and issues are known, others must be estimated. Estimation is an art, with many fine points to finesse between certainty and wishful thinking. You can't just hope you have the resources needed to do the job, and you can't just wait until every resource is available to begin.  Instead, you must take proactive steps to manage and mitigate using informed assumptions and constraints.

"A picture is worth a thousand words". Get an illustrated view of the project definition process in our infographic: Project Definition: Making Projects Ready for Action and Approval

Assumptions = Possibilities. Constraints = Limits.

Assumptions and constraints form a foundational basis for project planning, filling in the gaps between known proven facts and total guesswork.  Each assumption is an "educated guess", a likely condition, circumstance or event, presumed known and true in the absence of absolute certainty. Each constraint is a limiting condition, circumstance or event, setting boundaries for the project process and expected results.

Aside from the consequences, effective planning demands that varied types of assumptions and constraints be considered, as illustrated in the following list:

What are the possible assumptions and known constraints regarding.....?
  • THE EFFORT: The estimated tasks and activities required to manage the project and produce deliverables.
  • THE SCHEDULE: The estimated tasks and events needed to complete the project.
  • THE RESOURCE POOL:  The estimated staff resources needed to complete the project.
  • THE BUDGET: The estimated cost of the project, allocated to tasks, resources and phases.
  • THE CONTRACTS: The anticipated performance of contractors, vendors and suppliers.
  • THE PROCESS: The use and applicability of available management standards.

As assumptions and constraints are defined (as discussed below), each of the "types" listed above must be considered to ensure both comprehensive results and realistic approaches.

Assumptions and Constraints "To-Do List"

Identification is the first step in planning and managing known "assumptions and constraints".

Identify and Challenge - As assumptions are identified, each must be viewed with an appropriate degree of skepticism. Assumptions cannot be mere guesswork or wishful thinking. 

  • For example, you can't just hope that the budget will be sufficient, you have to examine and verify budget estimates to get as close to certainty as possible.
  • In turn, constraints must also be viewed skeptically, with an eye towards possible elimination. Constraints pose restrictions, and any relief from these restrictive elements would be welcome.
  • But, if constraints cannot be eliminated, then appropriate workarounds must be developed.

Assumptions should be evaluated from a long term perspective.

Evaluate - Analyze according to confidence level (i.e. How confident are you that this assumption will be proven correct), followed by a related "if-then" risk counterpart analysis (i.e. If this assumption is proven incorrect, what will be the likely consequences for the project?).

  • During the course of this analysis, the "impact of the incorrect assumption" must be determined. Impact can be weighed at various levels, from serious (threatening successful or timely project delivery), to moderate (absorbable impact on deliverables, schedules or costs), to minor (insignificant impact on deliverables, schedules or costs).
  •  Depending upon the assessed confidence level and related impact, a full risk assessment may be required. If you have high degree of confidence that a given assumption is true, then further analysis may be unwarranted. Lower confidence and higher impact would probably require further analysis and the related risk assessment.

In contrast, constraints must be evaluated from a short term perspective, according to immediate impact - i.e. How does a given constraint limit or refine the project in one or more respects? For example, product availability constraints can impact multiple elements of a single project. Product delays can elongate the project schedule, add to costs, and negatively impact resource availability. As constraints are assessed, all points of impact must be determined.

Once assumptions and constraints are identified and assessed, they must be incorporated into the relevant portion of the project plan.

Incorporate - Assumptions, combined with known facts, will drive the formation of the project plan, providing the actionable basis (albeit with varying degrees of certainty) for planned tasks, schedules, budgets and resource assignments.

  • Constraints must be factored into the project plan from the start in the form of stated "workarounds".
  • These workarounds will mitigate constraint "impact" by providing the means for the project to move ahead despite the existence of constraining factors (i.e. A schedule change allows for concurrent, non-dependent work to proceed even if there are delays in product delivery. This scheduling workaround will prevent an overall schedule delay).

Unidentified constraints will not just disappear, they will likely pop up at some later point as full fledged project problems. Consider this example: You are working on a project where specialized technical skills are required. You estimate that these specialized resources will be required for (40) hours per week during the month of June, and you prepare your project plan based on this assumption. However, you fail to account for the fact that these resources will only be available for (20) hours per week in the month of June. Initially, this resource limitation was a constraint, but since it was not identified at the outset, once June rolls around, it becomes a major problem.

Initial assumptions and constraints are rarely static.

Control - As the project evolves, assumptions will be proven true or untrue. Changing circumstances may eliminate or modify previously identified constraints. In either case, you must be prepared to react, with contingencies, workarounds and modifications to plans and deliverables.

  • To ensure a constant state of readiness, identified assumptions and constraints must be tracked and monitored throughout the project process.
  • In addition, assumptions can be factored into the plan via checkpoints (i.e. the point at which the assumption will be tested (proven correct or incorrect (in part or whole). These checkpoints can then be monitored to ensure that working assumptions are valid, and if not, to take corrective action.

Once a project is complete, assumptions and constraints should be reviewed as part of an overall "post-project" review process.

Review - To evaluate all steps taken for identification, assessment, incorporation and control.

  • Standardized project reviews incorporate "assumptions and constraints" considering quality, accuracy, effectiveness, and omissions (missed assumptions and/or constraints that should have been discovered as the project began).

From project initiation through closure, established assumptions and known constraints set the stage for project planning and execution. As the project proceeds, assumptions and constraints will be used to define and shape tasks, schedules, resource assignments and budget allocations. In this manner, each identified assumption and existing constraint forms a framework to be used to manage an otherwise uncertain future, laying out a roadmap for how the project will proceed.

Get our free ITtoolkit Project Management Glossary (PDF download).  Learn the lingo and language of "projects" from a practical, "big picture" point of view.

Continue reading more about assumptions, constraints and related issues:

About Us - ITtoolkit.com has been around since 2001. We started with a few articles about IT projects, and since then have developed our own series of time-saving practices and Toolkits for managing projects and IT services. The article above is part of of our full catalog of "how-to" articles, filled with these techniques (which you won't find elsewhere) to help you get better results in less time.  We cover all the basics and then some - including projects, IT services, team building, disaster recovery and more. You can continue with our recommendations above, browse the articles catalog, or download free templates and whitepapers.  And, visit our home page to learn all that our Service Strategy and Fast Track Project Toolkits can do for you!

Subscribe to the ITtoolkit newsletter for the latest articles and updates.

See the latest in our collection of IT Management Infographics. Visualize I.T.!

Get the "Value of a Vision" with the IT Service Strategy Toolkit

The IT Service Strategy Toolkit, from ITtoolkit.com, is the ultimate how-to guide for managing IT according to a strategic vision.  And what's the value of a vision?  Maximized IT value, optimized service capabilities, satisfied end-users and lasting IT/business alignment.  And it's all so easy to achieve with our downloadable Service Strategy Toolkit:

Make IT More Relevant!
Learn how to create your own IT management vision, covering how your IT department is organized, the types of services provided, Service Level Agreements, and more.
Make IT More Responsive!
Learn how to promote your vision through multiple organizational techniques including the IT/End-User Partnership, IT Steering Committees,  IT "stakeholder analysis", end-user roles in IT projects, and more.
Make IT More Productive!
Learn how to keep your vision going as IT services are provided, including standardized practices for projects, IT planning, and proactive problem management.
Make IT More Accepted!
Learn how to plan and execute timely, relevant 'IT Service Reviews' to determine end-user "service satisfaction" and uncover valuable lessons learned for service improvement.

The Top 10 Uses for a Strategic IT Vision

Make Projects Possible with the Fast Track Project Toolkit

What's a manager to do when faced with an important project and a big problem - namely, not enough time, resources or funding?  That's a big (and all too common) challenge, but there is an answer.  All you need to do is "fast track" your way over every obstacle with our FAST TRACK PROJECT TOOLKIT, (and it's available now at fasttrackmanage.com).

Take on the Challenge of the Project Constraint!
Learn how to use strategic fast tracking to deliver on-time projects when time is short, resources are stretched thin and funding is limited.
Negotiate.  Define.  Meeting of the Minds!
Learn how to quickly define projects for action and approval, using (16) must-have "terms" designed to secure stakeholder acceptance and ensure relevant results.
Make the Process Fit the Project!
Learn how to "size" governance practices to optimize resource capabilities, covering all the key steps for managing risk, project status reporting, communication, change control and more.
Always Look to Improve!
Learn how to perform effective "project reviews" to evaluate project results, and use the resulting "lessons learned" for continuous improvement.
Available for Download in 3 Editions!
And, when you get the "Bundle Edition" (the best value!), you also get a complete set of organizational practices for running successful PROJECT COMMITTEES.

Fast Track Project Toolkit