Scaled Agile Exam SAFe-RTE Topic 1 Question 27 Discussion

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

Question #: 27
Topic #: 1

[All SAFe-RTE Questions]

How often should a system demo occur?

AAfter the end of each program increment (Pl)

BAfter every other iteration

CAfter every release

DAfter every iteration

Show Suggested Answer

Suggested Answer: C

by Lizette at Apr 09, 2024, 04:16 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Cristina

3 months ago

How about a demo after every breath? Wait, that might be a bit excessive, even for an Agile team.

upvoted 0 times

...

Adelaide

3 months ago

Option B is the way to go. Every other iteration is a nice balance between frequent updates and not overdoing it.

upvoted 0 times

Janine

1 months ago

It's important to have regular demos to showcase progress.

upvoted 0 times

...

Louvenia

2 months ago

I think after every iteration is too frequent, it might be too much information for stakeholders to digest.

upvoted 0 times

...

Arthur

2 months ago

D) After every iteration

upvoted 0 times

...

Gerald

2 months ago

I agree, it allows for progress to be shown regularly without overwhelming stakeholders.

upvoted 0 times

...

Kristel

2 months ago

I think having a demo after every other iteration keeps everyone informed.

upvoted 0 times

...

Trina

2 months ago

B) After every other iteration

upvoted 0 times

...

Oneida

2 months ago

I agree, option B seems like a good balance.

upvoted 0 times

...

Edgar

3 months ago

After every release sounds good to me. That way we can demonstrate the final product and not get bogged down with work-in-progress.

upvoted 0 times

Amie

2 months ago

C) After every release

upvoted 0 times

...

Jesus

2 months ago

B) After every other iteration

upvoted 0 times

...

Amos

2 months ago

A) After the end of each program increment (PI)

upvoted 0 times

...

Viva

3 months ago

I'm going with option D - after every iteration. That way we can catch issues early and make adjustments as we go.

upvoted 0 times

Merissa

2 months ago

I think having demos after every iteration is a good way to stay on top of things.

upvoted 0 times

...

Tula

2 months ago

I agree, it's better to have frequent demos to ensure everything is on track.

upvoted 0 times

...

Delbert

2 months ago

That sounds like a good plan. It's important to catch any issues early on.

upvoted 0 times

...

Rima

4 months ago

Hmm, I'd say after each PI, that way we can showcase the progress and get feedback from stakeholders.

upvoted 0 times

Jospeh

3 months ago

I think after every iteration is too frequent, we might not have enough to show for a demo.

upvoted 0 times

...

Brock

3 months ago

I agree, it's important to get feedback regularly to make sure we're on track.

upvoted 0 times

...

Bettina

4 months ago

I prefer having a demo after every release, it allows for a more comprehensive review of the system.

upvoted 0 times

...

Stacey

4 months ago

I agree with Nidia, having a demo after every iteration helps in getting feedback early on.

upvoted 0 times

...

Nidia

4 months ago

I think a system demo should occur after every iteration.

upvoted 0 times

...