Scaled Agile SAFe-RTE Exam - 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

Jules

9 months ago

I’m not sure D is practical. What if the iterations are too short?

upvoted 0 times

...

Marshall

9 months ago

Wait, after every iteration? That seems like a lot!

upvoted 0 times

...

Valentin

10 months ago

A is more realistic for larger projects, though.

upvoted 0 times

...

Filiberto

10 months ago

Totally agree with D! Regular demos are key for feedback.

upvoted 0 times

...

Loren

10 months ago

I think D is the best option. After every iteration keeps everyone in the loop.

upvoted 0 times

...

Mari

10 months ago

I thought it was after every iteration too, but I wonder if there are cases where it could be less frequent, like after every other iteration?

upvoted 0 times

...

Izetta

10 months ago

I feel like I've seen practice questions where the answer was after every release, but that seems too infrequent for feedback.

upvoted 0 times

...

Buck

11 months ago

I remember studying that demos are usually tied to program increments, but I can't recall if that's the only time they should happen.

upvoted 0 times

...

Jeff

11 months ago

I think system demos should happen after every iteration, but I'm not completely sure if that's the best practice.

upvoted 0 times

...

Linsey

11 months ago

I'd go with A. Doing a demo after each program increment allows the team to showcase their progress and get feedback, which is really important in an agile process.

upvoted 0 times

...

Ruthann

11 months ago

After every iteration seems too frequent to me. I'm leaning towards A or C, but I'm not 100% confident. Gotta re-read the question and options again.

upvoted 0 times

...

Suzi

11 months ago

Hmm, I'm not totally sure about this one. I'm debating between A and D, since both seem plausible. I'll have to think it through carefully.

upvoted 0 times

...

Tawny

11 months ago

I think the answer is A - after the end of each program increment. That makes the most sense to me since the demo would showcase the work done in that increment.

upvoted 0 times

...

Buck

11 months ago

I think the International Accounting Standards Board is definitely one of them. I've seen it in practice questions before.

upvoted 0 times

...

Val

11 months ago

Hmm, I'm a bit unsure about this one. Root cause analysis is something we covered in class, but I can't quite remember all the details. I'll have to think it through carefully.

upvoted 0 times

...

Verda

11 months ago

The SAS Deployment Manager in option D seems like the most comprehensive tool for managing this type of change. I'd go with that.

upvoted 0 times

...

Walker

11 months ago

I'm a bit confused by the different options here. I'll need to re-read the question and the configuration details to make sure I'm understanding everything correctly before selecting an answer.

upvoted 0 times

...

Cristina

1 year ago

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

upvoted 0 times

...

Adelaide

1 year 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 year ago

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

upvoted 0 times

...

Louvenia

1 year ago

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

upvoted 0 times

...

Arthur

1 year ago

D) After every iteration

upvoted 0 times

...

Gerald

1 year ago

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

upvoted 0 times

...

Kristel

1 year ago

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

upvoted 0 times

...

Trina

1 year ago

B) After every other iteration

upvoted 0 times

...

Oneida

1 year ago

I agree, option B seems like a good balance.

upvoted 0 times

...

Edgar

1 year 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

1 year ago

C) After every release

upvoted 0 times

...

Jesus

1 year ago

B) After every other iteration

upvoted 0 times

...

Amos

1 year ago

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

upvoted 0 times

...

Viva

1 year 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

1 year ago

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

upvoted 0 times

...

Tula

1 year ago

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

upvoted 0 times

...

Delbert

1 year ago

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

upvoted 0 times

...

Rima

1 year ago

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

upvoted 0 times

Jospeh

1 year ago

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

upvoted 0 times

...

Brock

1 year ago

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

upvoted 0 times

...

Bettina

1 year ago

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

upvoted 0 times

...

Stacey

1 year ago

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

upvoted 0 times

...

Nidia

1 year ago

I think a system demo should occur after every iteration.

upvoted 0 times

...