Skip to content
CAPMHard

CAPM Practice: Demonstrate an understanding of the various project life cycles and processes

Question 67 of 95 in Demonstrate an understanding of the various project life cycles and processes

Pick an answer below — you'll get the explanation instantly, no signup.

Fatou Fujimoto is managing a software development project at Wavelength Biotech. During a meeting, she identifies that user requirements may change as clinical trials progress, the regulatory approval timeline is fixed at 18 months, and there is uncertainty about whether a key vendor can deliver on time. She also notes that a competitor recently launched a similar product. How should Fatou categorize these items?
Show answer & explanation

Correct answer: Changing requirements are an assumption, fixed timeline is a constraint, vendor uncertainty is a risk, and competitor launch is an issue

Explanation

An assumption is something believed to be true without proof (changing requirements may occur). A constraint is a limiting factor (fixed 18-month timeline). A risk is an uncertain event that could impact the project (vendor may not deliver on time). An issue is a current problem requiring action (competitor has already launched). Fatou correctly identifies: changing requirements as an assumption about future behavior, the fixed timeline as a constraint limiting flexibility, vendor uncertainty as a risk that may or may not occur, and the competitor launch as an issue that exists now.

**Why not A:** This option incorrectly classifies changing requirements as a risk rather than an assumption. Changing requirements are anticipated based on the nature of clinical trials — this is something believed likely to happen (an assumption), not an uncertain event. It also incorrectly classifies the competitor launch as an issue when it has already happened and represents a current reality requiring attention.

**Why not C:** This option incorrectly classifies changing requirements as a constraint and the fixed timeline as a risk. The fixed timeline is an imposed limitation (a constraint), not an uncertain event. Changing requirements reflect an expectation about future behavior (an assumption), not a restriction on project options.

**Why not D:** This option incorrectly classifies changing requirements as an issue, the fixed timeline as an assumption, and vendor uncertainty as a constraint. Changing requirements have not yet materialized as a current problem. The fixed timeline is imposed, not assumed. Vendor uncertainty is a future possibility (a risk), not a limitation on project options.

Key Concept

This question covers Demonstrate an understanding of the various project life cycles and processes under Demonstrate an understanding of the various project life cycles and processes (Project Management Fundamentals and Core Concepts).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free