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
3 months agoLeah
3 months agoCordelia
3 months agoTonja
4 months agoLenny
4 months agoMatthew
4 months agoEun
4 months agoViva
5 months agoLeonard
5 months agoCandida
5 months agoSylvia
5 months agoGail
5 months agoEthan
5 months agoJanine
5 months agoMaryrose
10 months agoLilli
10 months agoBernardine
9 months agoJulian
9 months agoCecily
9 months agoLaurel
10 months agoTonja
9 months agoJunita
9 months agoTonette
9 months agoGilma
10 months agoAlpha
9 months agoChan
10 months agoFrancene
10 months agoKallie
10 months agoJules
9 months agoYuette
9 months agoMammie
10 months agoSharika
10 months agoYolande
11 months agoAron
11 months agoBecky
11 months ago