Scaled Agile Exam SAFe-SPC Topic 2 Question 23 Discussion

Actual exam question for Scaled Agile's SAFe-SPC exam

Question #: 23
Topic #: 2

You organization decided to thoroughly implement the SAFe Principle "Assume variability; preserve options." What is the optimum path for success?

AAssume variability of scope and preserve options for the release date.

BPreserve flexibility in system functionality and design, but have fixed Solution intent.

CAssume variability of scope, but have fixed Solution Context.

DPreserve flexibility in both system functionality and design.

Show Suggested Answer

Suggested Answer: D

by Laurel at Aug 06, 2024, 07:06 AM

Limited Time Offer

25%

Off

Get Premium SAFe-SPC Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Vilma

3 months ago

Hey, I heard that 'assuming variability' is like assuming your coworker will forget to refill the coffee pot. Might as well just make your own brew, right?

upvoted 0 times

Rosalind

2 months ago

C) Assume variability of scope, but have fixed Solution Context.

upvoted 0 times

...

Alisha

2 months ago

B) Preserve flexibility in system functionality and design, but have fixed Solution intent.

upvoted 0 times

...

Reena

2 months ago

C) Assume variability of scope, but have fixed Solution Context.

upvoted 0 times

...

Ernie

3 months ago

B) Preserve flexibility in system functionality and design, but have fixed Solution intent.

upvoted 0 times

...

Anastacia

3 months ago

A) Assume variability of scope and preserve options for the release date.

upvoted 0 times

...

Sang

3 months ago

A) Assume variability of scope and preserve options for the release date.

upvoted 0 times

...

Alva

3 months ago

I'm going with D. Gotta keep those options open, baby! Variety is the spice of life, am I right?

upvoted 0 times

...

Emmanuel

3 months ago

Option C looks good to me. Assuming variability of scope while having a fixed solution context seems like a balanced approach.

upvoted 0 times

...

Anabel

3 months ago

Hmm, I'm torn between B and D. Preserving flexibility in the system functionality and design seems ideal, but I don't want to completely ignore the solution intent either.

upvoted 0 times

Martin

1 months ago

Let's go with D then. It's important to preserve flexibility in both system functionality and design.

upvoted 0 times

...

Rachael

1 months ago

I agree with you, D seems like the best option for success.

upvoted 0 times

...

Lorrine

2 months ago

I see your point, but I believe D is the better choice. Flexibility in both functionality and design is crucial.

upvoted 0 times

...

Sherill

3 months ago

I think B is the way to go. It's important to have a fixed Solution intent.

upvoted 0 times

...

Stephaine

4 months ago

I see both points, but I think preserving flexibility in system functionality and design, but having fixed Solution intent (B) strikes a good balance.

upvoted 0 times

...

Shayne

4 months ago

I disagree, I believe it's better to preserve flexibility in both system functionality and design (D).

upvoted 0 times

...

Catina

4 months ago

I think option D is the way to go. Preserving flexibility in both system functionality and design aligns perfectly with the SAFe principle of 'Assume variability; preserve options'.

upvoted 0 times

Mozell

2 months ago

That makes sense, it's all about finding the right balance between flexibility and stability.

upvoted 0 times

...

Gracia

2 months ago

I see your point, but having flexibility in both functionality and design can lead to better outcomes in the long run.

upvoted 0 times

...

Salley

3 months ago

But wouldn't it be better to have a fixed Solution Context to provide some stability?

upvoted 0 times

...

Pura

3 months ago

I agree, option D allows for adaptability while still having a clear solution intent.

upvoted 0 times

...

Daniela

4 months ago

I think the best path is to assume variability of scope and preserve options for the release date (A).

upvoted 0 times

...