In project planning, which statement best describes the relationship between a constraint and an assumption?

In project planning, which statement best describes the relationship between a constraint and an assumption?

• A. An assumption is a proven fact used for planning.
• B. A constraint is a condition that has no impact on schedule or cost.
• C. A constraint is a limitation that restricts options; an assumption is a factor believed true for planning but not verified, and both should be documented and monitored.
• D. Assumptions are external to the project and do not require monitoring.

Answer: (C)

In project planning, you separate what you know you must work within from what you believe to be true for planning. A constraint is a limitation that restricts options—like a fixed deadline, a fixed budget, or limited resources. An assumption is something you take to be true for planning but haven’t verified yet; you rely on it to develop schedules and estimates, with the understanding you’ll test and update it as you learn more. The strongest statement captures both ideas and emphasizes management: document both constraints and assumptions and monitor them as the project progresses. This helps you understand how limits shape your plan and how beliefs you’re counting on might change, reducing risk as you validate or adjust them. The other options fail because they either treat assumptions as proven facts, imply constraints have no impact, or say assumptions don’t require monitoring, all of which would undermine proper planning and risk management.

In project planning, you separate what you know you must work within from what you believe to be true for planning. A constraint is a limitation that restricts options—like a fixed deadline, a fixed budget, or limited resources. An assumption is something you take to be true for planning but haven’t verified yet; you rely on it to develop schedules and estimates, with the understanding you’ll test and update it as you learn more. The strongest statement captures both ideas and emphasizes management: document both constraints and assumptions and monitor them as the project progresses. This helps you understand how limits shape your plan and how beliefs you’re counting on might change, reducing risk as you validate or adjust them. The other options fail because they either treat assumptions as proven facts, imply constraints have no impact, or say assumptions don’t require monitoring, all of which would undermine proper planning and risk management.