What are the Scope Definition process tools and techniques?

Question

Options

• AProduct analysis, alternatives identification, expert judgment, and stakeholder analysis
• BAlternatives identification, stakeholder analysis, and expert judgment
• CProduct analysis, cost benefit analysis, alternatives identification, and expert judgment
• DCost benefit analysis, templates, and expert judgment

• A
  78% (32)
• B
  2% (1)
• C
  7% (3)
• D
  12% (5)

Explanation

Option A is correct because the Scope Definition process (per PMBOK) uses product analysis (decomposing deliverables to better understand them), alternatives identification (brainstorming different ways to meet objectives), expert judgment (leveraging subject matter expertise), and stakeholder analysis (ensuring all parties' needs are captured in the scope).

Option B is wrong because it omits product analysis, which is a core technique for breaking down and understanding the product being delivered. Option C is wrong because cost benefit analysis belongs to other processes (like quality planning or make-or-buy decisions), not Scope Definition. Option D is wrong for the same reason - cost benefit analysis doesn't belong here, and while templates can support documentation, they are not a listed tool/technique for this specific process.

Memory tip: Think "PASE" - Product analysis, Alternatives identification, Stakeholder analysis, Expert judgment - the four tools that help you define what the project will deliver by looking at the product, options, people, and knowledge available.

No community discussion yet for this question.