Where are product requirements and characteristics documented?

Question

Options

• AProduct scope description
• BProject charter
• CPreliminary project scope statement
• DCommunications management plan

• A
  77% (20)
• B
  4% (1)
• C
  8% (2)
• D
  12% (3)

Explanation

Product scope description (A) is correct because it is specifically the document that captures the characteristics and requirements of a product, service, or result - it defines what the product is and what it must do or include.

Why the distractors are wrong:

• B. Project charter - authorizes the project and names the project manager, but focuses on high-level objectives, business case, and stakeholder sign-off, not detailed product requirements.
• C. Preliminary project scope statement - is an early-stage document outlining the project's general boundaries and deliverables; it precedes detailed requirement documentation and is broader in scope.
• D. Communications management plan - describes how project information will be distributed, to whom, and when - it has nothing to do with product characteristics.

Memory tip: Think "product scope = product specs." If the question is about the product itself (what it does, what it looks like, what it must achieve), that lives in the product scope description. If it's about the project (who authorized it, how we'll manage it), look elsewhere.

No community discussion yet for this question.