A business analyst (BA) is working on a project that follows incremental and iterative approaches. The BA and the stakeholders have shortlisted several user stories to be considered in the project…

The correct answer is D. MoSCoW prioritization. MoSCoW prioritization is a technique that helps to classify requirements or user stories based on their relative importance and urgency. The acronym stands for Must have, Should have, Could have, and Won't have. This technique enables the business analyst (BA) and the…

Requirements Life Cycle Management

Question

A business analyst (BA) is working on a project that follows incremental and iterative approaches. The BA and the stakeholders have shortlisted several user stories to be considered in the project scope. Which of the following methods would enable them to arrive at a common understanding on delivering value in the product and ranking the stories?

Options

AStory decomposition
BState modelling
CValue stream mapping
DMoSCoW prioritization

How the community answered

(44 responses)

A
2% (1)
B
7% (3)
C
14% (6)
D
77% (34)

Explanation

MoSCoW prioritization is a technique that helps to classify requirements or user stories based on their relative importance and urgency. The acronym stands for Must have, Should have, Could have, and Won't have. This technique enables the business analyst (BA) and the stakeholders to agree on the minimum viable product (MVP) and the order of delivery for the project scope. MoSCoW prioritization also supports incremental and iterative approaches, as it allows for frequent feedback and validation of the product value.

Topics

#MoSCoW prioritization#user stories#agile#backlog management

Community Discussion

No community discussion yet for this question.

Full CCBA Practice