Scrum PSM-I Exam - Topic 4 Question 53 Discussion

Actual exam question for Scrum's PSM-I exam

Question #: 53
Topic #: 4

[All PSM-I Questions]

For the purpose of transparency, when does Scrum say a new increment of working software must be available?

AAfter the acceptance testing phase.

BBefore the release Sprint.

CEvery 3 Sprints.

DAt the end of every Sprint.

EWhen the Product Owner asks to create one.

Show Suggested Answer

Suggested Answer: D

by Detra at Apr 19, 2023, 09:49 AM

Limited Time Offer

25%

Off

Get Premium PSM-I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Honey

8 months ago

Really? I find that hard to believe.

upvoted 0 times

...

Fletcher

8 months ago

Nope, it's definitely every Sprint.

upvoted 0 times

...

Melissia

9 months ago

Wait, I thought it was before the release Sprint?

upvoted 0 times

...

Berry

9 months ago

Totally agree, D is the right answer.

upvoted 0 times

...

Kris

9 months ago

It's at the end of every Sprint!

upvoted 0 times

...

Annalee

9 months ago

I’m leaning towards saying it’s at the end of every Sprint, but I could be mixing it up with something else we studied.

upvoted 0 times

...

Mariann

9 months ago

I feel like the answer might be related to the Product Owner's requests, but that doesn't sound right for Scrum.

upvoted 0 times

...

Rodney

9 months ago

I remember practicing a question about when increments are delivered, and I think it was definitely not every 3 Sprints.

upvoted 0 times

...

Carissa

9 months ago

I think the increment has to be available at the end of every Sprint, but I'm not completely sure.

upvoted 0 times

...

Natalie

9 months ago

Hmm, this seems like a tricky one. I'll need to think through the different options carefully to make sure I understand the purpose of the Sync network.

upvoted 0 times

...

Thea

10 months ago

I've got a good strategy for this. I'll evaluate the epics and stones, then identify a set of user stories based on the team's velocity.

upvoted 0 times

...

Valene

1 year ago

Clearly, the answer is D. Scrum is all about shipping working software at the end of each Sprint. Anyone who thinks otherwise must be living in a different galaxy.

upvoted 0 times

Peggie

1 year ago

Yes, it's a core principle of Scrum to have a potentially shippable product increment at the end of each Sprint.

upvoted 0 times

...

Brendan

1 year ago

Absolutely, that's the essence of Scrum. Delivering value consistently.

upvoted 0 times

...

Joaquin

1 year ago

I agree, the answer is D. It's important to have a new increment of working software at the end of every Sprint.

upvoted 0 times

...

Nickolas

1 year ago

A) After the acceptance testing phase. Nope, that's not it. Scrum is about getting working software into the hands of users as quickly as possible, not waiting for lengthy testing cycles.

upvoted 0 times

...

Lauran

1 year ago

B) Before the release Sprint. Haha, no way! Scrum is all about continuous delivery, not waiting until the end to release.

upvoted 0 times

Tyisha

1 year ago

D) At the end of every Sprint.

upvoted 0 times

...

Leota

1 year ago

B) Before the release Sprint. Haha, no way! Scrum is all about continuous delivery, not waiting until the end to release.

upvoted 0 times

...

Rickie

1 year ago

D) At the end of every Sprint.

upvoted 0 times

...

Wilda

1 year ago

A) After the acceptance testing phase.

upvoted 0 times

...

Alishia

1 year ago

E) When the Product Owner asks to create one. Wait, what? That's not how Scrum works at all. The Product Owner doesn't just randomly demand an increment when they feel like it.

upvoted 0 times

Danica

1 year ago

B) Before the release Sprint.

upvoted 0 times

...

Linette

1 year ago

D) At the end of every Sprint.

upvoted 0 times

...

Gertude

1 year ago

A) After the acceptance testing phase.

upvoted 0 times

...

Jerilyn

1 year ago

D) At the end of every Sprint. That's the whole point of the Scrum framework - to deliver a potentially shippable increment of working software at the end of each Sprint.

upvoted 0 times

Kate

1 year ago

B) Before the release Sprint.

upvoted 0 times

...

Fausto

1 year ago

A) After the acceptance testing phase.

upvoted 0 times

...

Malcom

1 year ago

D) At the end of every Sprint. That's the whole point of the Scrum framework - to deliver a potentially shippable increment of working software at the end of each Sprint.

upvoted 0 times

...

Niesha

1 year ago

C) Every 3 Sprints. I think having a new increment of working software every 3 Sprints allows for more time to work on larger features and improvements.

upvoted 0 times

...

Nickolas

1 year ago

I agree with Jettie. Having a new increment of working software at the end of every Sprint helps in getting feedback and making necessary adjustments.

upvoted 0 times

...

Jettie

1 year ago

D) At the end of every Sprint. It's important to have a new increment of working software at the end of each Sprint to show progress.

upvoted 0 times

...