ECBA practice question 20 of 25

When should prioritization of requirements take place?

Full set: 210 questions
Answer options
A: At the very beginning of an initiative only
B: After the maintain requirements and trace requirements tasks have been completed
C: Continually throughout the initiative Correct answer
D: After the maintain requirements task has been completed
Correct Answer:
C. Continually throughout the initiative
Explanation

Requirements prioritization is not a single event but an ongoing process performed throughout an initiative. Initial priorities may be set early, but they must be continuously re-evaluated as the project context evolves, new information is discovered, risks change, and stakeholder needs are better understood. This iterative approach ensures that the development effort remains focused on delivering the highest value at any given point in the project lifecycle. The BABOK® Guide explicitly states that prioritization is a continuous activity to manage scope and adapt to change effectively.

Why Incorrect

A. Prioritizing only at the beginning is rigid and fails to adapt to the inevitable changes in understanding, context, and stakeholder needs during an initiative.
B. Prioritization is a prerequisite for many subsequent activities; waiting for maintenance and tracing to be "completed" is illogical as these are also ongoing tasks.
D. The 'Maintain Requirements' task includes managing changes and attributes, which often involves re-prioritization; it is not an activity that must be completed beforehand.

References

1. IIBA

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)

Version 3

2015.

Section 5.3.2 (Description): "Prioritization is an ongoing process to ensure that the team is focused on the most critical requirements at any given time. Business analysts facilitate the prioritization process with stakeholders." This directly supports the continuous nature of the task.

Section 5.1.2 (Description): In the 'Trace Requirements' task

it is mentioned that relationships between requirements can "assist in managing changes to requirements by helping to identify the upstream and downstream effects of a proposed change"

which often triggers re-prioritization.

Section 5.2.4.2 (Maintain Attributes): "As requirements are elaborated

new attributes may be identified and existing attribute values may change." A key attribute is priority

reinforcing that it is maintained and updated over time.

Scroll to Top