I've got a good feeling about this one. The key is understanding how Stories work together to support a workflow or address different user needs. I think I can narrow it down from there.
Based on the options, it seems like a Story map would be used when the Stories span multiple teams or when there are multiple personas to consider. I'll focus on those possibilities.
Okay, let me see. I think it has to do with how the Stories are related to each other, like if they're part of a larger workflow or if they're dependent on one another.
I'm not sure, but I think creating a Story map when Stories are dependent on one another could also be a good reason. Option D might be a valid choice.
I'm not sure about that. Option D looks more like the correct answer to me. When Stories are dependent on one another, a Story map can help manage those dependencies.
Option C seems to be the correct answer. When Stories for a single Feature span multiple teams, a Story map can help visualize the dependencies and flow.
Lenita
5 months agoLeah
5 months agoCordelia
5 months agoTonja
5 months agoLenny
6 months agoMatthew
6 months agoEun
6 months agoViva
6 months agoLeonard
6 months agoCandida
6 months agoSylvia
6 months agoGail
6 months agoEthan
6 months agoJanine
6 months agoMaryrose
11 months agoLilli
11 months agoBernardine
10 months agoJulian
10 months agoCecily
10 months agoLaurel
12 months agoTonja
11 months agoJunita
11 months agoTonette
11 months agoGilma
12 months agoAlpha
11 months agoChan
11 months agoFrancene
11 months agoKallie
1 year agoJules
11 months agoYuette
11 months agoMammie
11 months agoSharika
12 months agoYolande
1 year agoAron
1 year agoBecky
1 year ago