HKSM

Assumption and constraint analysis is a structured review of what is believed to be true without proof and the limits that restrict the project. It validates realism, reveals risks and trade-offs, and guides planning decisions.

Key Points

• Assumptions are things accepted as true for planning; constraints are limits the project must operate within.
• The technique tests realism and identifies risks, dependencies, and required trade-offs.
• Apply it early during initiation and planning, then revisit at each major change or review point.
• Document results in an assumption log with owners, dates, and validation or monitoring actions.
• Constraints may be budget caps, deadlines, compliance rules, resource limits, or technology boundaries.
• Invalidated assumptions can become issues; overly tight constraints may trigger change requests.

Purpose of Analysis

The analysis makes hidden beliefs and hard limits explicit so the team can plan realistically. It reduces surprises, improves estimates, and aligns stakeholders on what must be true and what cannot change.

Method Steps

• Identify assumptions and constraints from stakeholders, documents, and expert input.
• Classify items by category (technical, resource, contractual, regulatory, schedule, cost).
• Assess each item for validity, impact, and likelihood of change; note dependencies.
• Define validation or monitoring actions (e.g., proof-of-concept, vendor confirmation, legal review).
• Record items in the assumption log with owners, due dates, and response strategies.
• Link high-impact items to risks and integrate responses into plans and baselines.
• Review and update regularly; escalate changes as issues or change requests when needed.

Inputs Needed

• Business case and project charter.
• Stakeholder inputs and subject matter expert opinions.
• Requirements, scope details, and solution options.
• Contracts, procurement strategies, and compliance policies.
• Organizational process assets and historical data from similar work.
• Enterprise environmental factors such as market conditions and resource availability.

Outputs Produced

• Updated assumption log and constraint inventory with owners and actions.
• Risk register updates and proposed risk responses.
• Planning adjustments to scope, schedule, cost, and resource plans.
• Change requests when constraints or invalid assumptions require baseline changes.
• Decision log entries capturing approvals and trade-offs.

Interpretation Tips

• Challenge absolutes like "must" and "cannot" to confirm if they are true constraints or preferences.
• Quantify the effect of each item on time, cost, scope, and quality to set priorities.
• Seek evidence for critical assumptions; time-box validations to avoid analysis paralysis.
• Use scenario and sensitivity analysis to understand how changes might affect outcomes.
• Assign clear ownership for validation and monitoring; track due dates visibly.

Example

A project plans to deliver a new service by June with a fixed budget. The team lists an assumption that a key subject matter expert will be available 50% of the time, and a constraint that the go-live date is tied to a regulatory milestone.

Analysis reveals the expert is likely available only 25%, creating a risk to schedule. The team adds mitigation (cross-train a backup, adjust tasks) and raises a change request to add contractor hours. The regulatory date remains non-negotiable, so the schedule is re-sequenced to protect compliance-related tasks.

Pitfalls

• Treating opinions as facts without validation.
• Listing items once and never revisiting them as the project evolves.
• Failing to link high-impact items to risks, actions, or change control.
• Ignoring soft constraints like organizational capacity that still limit options.
• Overloading the log with low-impact noise that distracts from critical items.

PMP Example Question

During planning, the sponsor insists on a fixed end date. The team also assumes a new tool will be approved within two weeks. What should the project manager do first?

1. Extend the schedule to add contingency for the tool approval.
2. Record the date as an assumption and proceed with detailed planning.
3. Validate the tool approval assumption and classify the fixed date as a constraint in the log.
4. Escalate to the sponsor to negotiate a flexible end date.

Correct Answer: C — Validate the tool assumption and record the fixed end date as a constraint.

Explanation: The technique requires identifying, classifying, and validating assumptions while documenting constraints. This informs realistic planning and subsequent risk or change actions.