CAPM Practice: Determine how to gather requirements

Assumptions are beliefs taken as true without proof. If undocumented, they become hidden risks — projects can fail when assumptions prove false. Documenting assumptions makes them visible for validation and allows teams to develop contingency plans.

**Why not A:** An unapproved feature request is a stated desire from a stakeholder, not an assumption. Assumptions are factors believed to be true but not yet confirmed, whereas feature requests are explicit inputs that go through prioritization and approval processes.

**Why not B:** A technical constraint from a development team is a known limitation, not an assumption. Constraints are verified restrictions that shape solution design, while assumptions are unverified beliefs that carry risk and need to be validated throughout the project.

**Why not D:** A proven fact that everyone agrees on is the opposite of an assumption. Assumptions are specifically things that are believed to be true but have not yet been proven. Once something is validated and accepted as fact, it no longer carries the uncertainty that defines an assumption.