What is 'requirement volatility' and how should agile business analysts manage it in collaboration with stakeholders?
-
A
Requirements that are too vague; resolve by writing detailed specs upfront
-
B
Frequent changes to requirements; manage by embracing change through iterative refinement and backlog grooming
-
C
Requirements that conflict between stakeholders; resolve by majority vote
-
D
Requirements that are technically impossible; remove them from the backlog