nerdexam
IIBA

CBAP · Question #70

You are the business analyst for a large project in your organization. You are working with Ben to create requirements packages to present to the stakeholders, the business analyst team, and to the…

The correct answer is B. To convey information clearly and in an understandable fashion. The primary goal of a requirements package is to communicate requirements clearly and in a way that all intended audiences can understand.

Requirements Analysis and Design Definition

Question

You are the business analyst for a large project in your organization. You are working with Ben to create requirements packages to present to the stakeholders, the business analyst team, and to the project manager. Ben wants to know why you're creating requirements packages. What's the primary goal of developing a requirements package?

Options

  • ATo convey the cost, schedule, and risk information clearly
  • BTo convey information clearly and in an understandable fashion
  • CTo present the requirements in packages that are easy for the project team to accomplish in
  • DTo help the project manager create the work breakdown structure

How the community answered

(32 responses)
  • A
    9% (3)
  • B
    84% (27)
  • C
    3% (1)
  • D
    3% (1)

Why each option

The primary goal of a requirements package is to communicate requirements clearly and in a way that all intended audiences can understand.

ATo convey the cost, schedule, and risk information clearly

Cost, schedule, and risk information are project management concerns communicated through project plans and status reports, not requirements packages.

BTo convey information clearly and in an understandable fashionCorrect

Requirements packages are prepared and structured specifically to convey information clearly and in an understandable fashion to diverse audiences including stakeholders, project teams, and management. The packaging format and content are chosen based on the audience's needs, making clarity and comprehension the central objective.

CTo present the requirements in packages that are easy for the project team to accomplish in

Organizing work into accomplishable iterations is a sprint or release planning activity, not the purpose of a requirements package.

DTo help the project manager create the work breakdown structure

Creating a WBS is the project manager's responsibility and is not an outcome or goal of developing a requirements package.

Concept tested: Purpose and goal of requirements packages

Source: https://www.iiba.org/standards-and-resources/babok/

Topics

#requirements packages#stakeholder communication#requirements presentation#documentation

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CBAP Practice