MENU
For the purpose of transparency, when does Scrum say a new increment of working software must be available?
Suggested Answer: D
Get Premium PSM-I Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
HO
Honey
11 months ago
Really? I find that hard to believe.
FL
Fletcher
11 months ago
Nope, it's definitely every Sprint.
ME
Melissia
12 months ago
Wait, I thought it was before the release Sprint?
BE
Berry
12 months ago
Totally agree, D is the right answer.
KR
Kris
12 months ago
It's at the end of every Sprint!
AN
Annalee
1 year 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.
MA
Mariann
1 year ago
I feel like the answer might be related to the Product Owner's requests, but that doesn't sound right for Scrum.
RO
Rodney
1 year ago
I remember practicing a question about when increments are delivered, and I think it was definitely not every 3 Sprints.
CA
Carissa
1 year ago
I think the increment has to be available at the end of every Sprint, but I'm not completely sure.
NA
Natalie
1 year 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.
TH
Thea
1 year 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.
VA
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.
PE
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.
BR
Brendan
1 year ago
Absolutely, that's the essence of Scrum. Delivering value consistently.
JO
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.
NI
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.
LA
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.
TY
Tyisha
1 year ago
D) At the end of every Sprint.
LE
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.
RI
Rickie
1 year ago
D) At the end of every Sprint.
WI
Wilda
1 year ago
A) After the acceptance testing phase.
AL
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.
DA
Danica
1 year ago
B) Before the release Sprint.
LI
Linette
1 year ago
D) At the end of every Sprint.
GE
Gertude
1 year ago
A) After the acceptance testing phase.
JE
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.
KA
Kate
1 year ago
B) Before the release Sprint.
FA
Fausto
1 year ago
A) After the acceptance testing phase.
MA
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.
NI
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.
NI
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.
JE
Jettie
2 years 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.