Many organizations categorize requirements into which of the following two categories?

Question

Options

• AProject and Product
• BStaffing and Budget
• CStakeholder and Customer
• DBusiness and Technical

• A
  81% (22)
• B
  11% (3)
• C
  4% (1)
• D
  4% (1)

Explanation

Option A is correct because in standard project management and business analysis frameworks (including PMI's PMBOK and BABOK), requirements are commonly divided into project requirements (conditions the project must meet - timelines, governance, constraints) and product requirements (features and capabilities the deliverable must have). This two-category split is a foundational concept in requirements management.

Why the distractors are wrong:

• B (Staffing and Budget) - these are resource/cost planning elements, not requirement categories.
• C (Stakeholder and Customer) - these are roles who provide requirements, not categories of requirements themselves.
• D (Business and Technical) - while this split is used in some contexts, it is not the standard two-category framework taught in major PM/BA certifications.

Memory tip: Think "Project vs. Product" as how we do it (project) vs. what we build (product) - the project requirements govern the work, the product requirements describe the outcome.

No community discussion yet for this question.