define-a-project-assumption

name	define-a-project-assumption
category	start
description	Define a project assumption with its basis, uncertainty, dependency, impact, test, owner, and decision deadline. Use when a plan relies on something not yet proven.

define-a-project-assumption

Turn hidden certainty into a testable planning statement.

When to use

• Use during estimation, planning, design, procurement, launch, or recovery.
• Do not record a known fact, requirement, constraint, or unresolved issue as an assumption.

Procedure

1. State the assumption precisely and identify the plan or decision that relies on it.
2. Record source, date, evidence, confidence, and what remains unknown.
3. Describe the consequence if it is false, including time, cost, safety, quality, scope, or stakeholder effect.
4. Link dependencies, related risks, constraints, and affected milestones.
5. Define the cheapest reliable test, success criteria, owner, and deadline before the decision becomes expensive.
6. Record contingency or plan change if invalidated.
7. Update status to untested, testing, validated, invalidated, expired, or superseded with evidence.

Done

• An assumption record documents statement, basis, confidence, dependency, impact, test, owner, deadline, and contingency
• Fact-versus-assumption, evidence, success-criteria, decision-date, status, and plan-link checks verify it is actionable