When should prioritization of requirements take place?

Question

Options

• AAt the very beginning of an initiative only
• BAfter the maintain requirements and trace requirements tasks have been completed
• CContinually throughout the initiative
• DAfter the maintain requirements task has been completed

• A
  3% (1)
• B
  3% (1)
• C
  94% (30)

Explanation

Prioritization of requirements is an ongoing activity that must happen continually throughout an initiative because business needs, stakeholder priorities, and constraints evolve over time - a requirement critical at project start may become obsolete, and new high-priority requirements can emerge at any stage.

Why the distractors are wrong:

• A is wrong because doing it only at the beginning ignores changes in scope, resources, or business conditions that inevitably occur.
• B is wrong because prioritization is not gated behind other tasks - it operates in parallel with and independent of tracing/maintaining activities, and waiting would delay critical decisions.
• D is wrong for the same reason as B; tying prioritization to the completion of any single task creates an artificial dependency that doesn't reflect real practice.

Memory tip: Think of prioritization like a GPS - it doesn't just set your route once at the start; it recalculates continuously as conditions change. "Continually" = correct.

No community discussion yet for this question.