Discuss Scaled Agile SAFe-APM Exam Topic 2 Question 24

What circumstance would a team create a Story map?

AWhen Stories work together to support a workflow

BWhen the Feature has multiple personas to address

CWhen Stories for a single Feature span multiple teams

DWhen Stories are dependent on one another

Suggested Answer: D

The strategic sweet spot of a company is where it meets customer's needs in a way that rivals can't, given the context in which it competes12. It is where the company's capabilities match customer needs in a way that the competition can't. Finding the strategic sweet spot is a key challenge of strategic thinking and a source of competitive advantage.

How to find your strategic sweet spot and why it matters

The Strategic Sweet Spot - Harvard Business Review

Get Premium SAFe-APM Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

35 comments · newest first

Lenita 11 months ago

I thought Story maps were only for single Features, interesting!

Leah 11 months ago

Wait, are we sure it's not just for dependent Stories?

Cordelia 11 months ago

I agree, multiple teams can also create a Story map.

Tonja 11 months ago

I think it's more about multiple personas.

Lenny 12 months ago

Definitely when Stories work together to support a workflow!

Matthew 12 months ago

I keep mixing up the scenarios, but I think C makes sense if the stories are spanning across teams. That sounds familiar!

Eun 12 months ago

I thought we learned that Story maps are useful when addressing multiple personas, so B could be the right choice.

Viva 1 year ago

I'm not entirely sure, but I feel like we practiced a question similar to this, and it was about dependencies, which might point to D.

Leonard 1 year ago

I remember we discussed Story maps in class, and I think they help visualize how different stories fit together, so maybe it's A?

Candida 1 year ago

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.

Sylvia 1 year ago

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.

Gail 1 year ago

I'm a bit confused on the difference between a Feature and a Story. Does that matter for this question?

Ethan 1 year ago

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.

Janine 1 year ago

Hmm, this seems like a tricky one. I'll need to think through the different scenarios where a team might create a Story map.

Maryrose 1 year ago

I'm leaning towards Option C as well. It makes the most sense in terms of using a Story map to coordinate work across multiple teams.

Lilli 1 year ago

Haha, Option A is like saying we should create a Story map when the Stories decide to go on a field trip together. That's not how it works, folks.

Bernardine 1 year ago

↳ replying to Lilli

C) When Stories for a single Feature span multiple teams

Julian 1 year ago

↳ replying to Lilli

B) When the Feature has multiple personas to address

Cecily 1 year ago

↳ replying to Lilli

A) When Stories work together to support a workflow

Laurel 1 year ago

Wait, are we supposed to create a Story map when the Feature has multiple personas? That's like trying to herd cats! Option B is ridiculous.

Tonja 1 year ago

↳ replying to Laurel

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.

Junita 1 year ago

↳ replying to Laurel

I agree, it's important for the Stories to flow smoothly. Option A is definitely the way to go.

Tonette 1 year ago

↳ replying to Laurel

I think we should create a Story map when Stories work together to support a workflow. Option A seems like the best choice.

Gilma 1 year ago

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.

Alpha 1 year ago

↳ replying to Gilma

I agree, both Option D and Option A are valid reasons for creating a Story map.

Chan 1 year ago

↳ replying to Gilma

I think Option A is also a valid reason for creating a Story map. Stories working together to support a workflow is important.

Francene 1 year ago

↳ replying to Gilma

Option D looks like the correct answer. A Story map can help manage dependencies between Stories.

Kallie 2 years ago

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.

Jules 1 year ago

↳ replying to Kallie

Definitely, it can improve collaboration and coordination among teams.

Yuette 1 year ago

↳ replying to Kallie

It helps to see the big picture and understand the dependencies.

Mammie 1 year ago

↳ replying to Kallie

Yes, when Stories for a single Feature span multiple teams, a Story map can be really helpful.

Sharika 1 year ago

↳ replying to Kallie

I think option C is the best choice.

Yolande 2 years ago

But what about when Stories for a single Feature span multiple teams? Wouldn't that also be a reason to create a Story map?

Aron 2 years ago

I agree with Becky. It helps in visualizing the flow of work and dependencies.

Becky 2 years ago

I think a team would create a Story map when Stories work together to support a workflow.

Scaled Agile SAFe-APM Exam - Topic 2 Question 24 Discussion