Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum PSPO-I Exam - Topic 1 Question 5 Discussion

Posted by Tawna on Nov 26, 2023 at 11:17 AM

When might a Sprint be cancelled?

(choose the best answer)

Suggested Answer: D

A Sprint may be cancelled when the Sprint Goal becomes obsolete. This is because:

The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.

The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a ''Done'' Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints.

A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.

A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.

When a Sprint is cancelled, any completed and ''Done'' Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.

Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.


[Scrum Guide], page 15, section ''Sprint Goal''

[Scrum Guide], page 9, section ''Sprint''

[Scrum Guide], page 16, section ''Cancelling a Sprint''

Get Premium PSPO-I Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
17 comments · newest first
BA
Barb 11 months ago
B seems too vague, it shouldn't be a reason to cancel.
DA
Dallas 11 months ago
Surprised that people think a Sprint can be cancelled for sales opportunities!
SH
Shenika 11 months ago
I think option A is also valid, but not the best choice.
EL
Elenor 11 months ago
Totally agree, option D makes the most sense!
AM
Amira 11 months ago
A Sprint can be cancelled if the goal is no longer relevant.
TR
Tran 12 months ago
I recall discussing how external factors, like new opportunities, shouldn't affect the Sprint. So, I think D is the best choice.
ME
Melda 12 months ago
I feel like the answer might be about not finishing everything by the end of the Sprint, but that seems too common.
EV
Evette 12 months ago
I'm not entirely sure, but I remember something about the product plan being infeasible. That could be a reason too, right?
BR
Brent 1 year ago
I think a Sprint can be cancelled if the Sprint Goal becomes obsolete, like when priorities shift. That sounds familiar from our last practice quiz.
DA
Darnell 1 year ago
Ah, this is a tricky one. I'm not sure if the sales department getting a new opportunity would be a valid reason to cancel a Sprint. I'll have to review the Scrum principles again to be sure.
KA
Kayleigh 1 year ago
Hmm, I'm a bit unsure about this one. I think it might be when the Sprint Goal becomes obsolete, but I'm not totally sure. I'll have to think it through carefully.
PE
Pete 1 year ago
This seems like a straightforward question about Scrum. I'm pretty confident I know the answer - it's when the Developers determine the product plan is infeasible.
JA
Jacquelyne 1 year ago
Okay, let me see... I remember from the Scrum Guide that a Sprint can be cancelled if it's clear the team won't finish everything by the end. I think that's the best answer here.
LE
Lennie 1 year ago
I think I've got this! The key is understanding that the traffic from Customer A and Customer B is classified to the same forwarding class, so it gets queued together at the ingress of Router B. The diagram clearly shows the direction of traffic flow, so I'm confident the statement is true.
QU
Quentin 1 year ago
Okay, I think I've got a handle on this. I'll start by checking if the topology is too complex or has too much concurrency, which could be causing startup issues. Then I'll look at the supervisor's resource allocation to see if that's the problem.
HA
Harley 1 year ago
The solution mentions federating both the tenant name and domain, so I'll go with that.
FE
Felix 1 year ago
This seems like a straightforward question about different order fulfillment processes. I think the key is to focus on the wording about "committing orders against available capacity as well as inventory". That sounds like it's describing a process that checks both production capacity and inventory levels.
0/2000 characters

Save Cancel