According to the Scrum Guide 1 , a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
[References: Scrum Guide, , , ]
Question 70
When can a Development Team cancel a Sprint?
Options:
A.
It can’t. Only Product Owners can cancel Sprints.
B.
When functional expectations are not well understood.
C.
When the Product Owner is absent too often.
D.
When the selected Product Backlog items for the Sprint become unachievable.
E.
When a technical dependency cannot be resolved.
Answer:
A
Explanation:
The correct answer is A, because the Scrum Guide states that “a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.” Therefore, a Development Team cannot cancel a Sprint by itself.
Question 71
If burndown charts are used to visualize progress, what do they track?
Options:
A.
Accumulated cost.
B.
Individual worker productivity.
C.
Work remaining across time.
D.
Accumulated business value delivered to the customer.
Answer:
C
Explanation:
The correct answer is C, because if burndown charts are used to visualize progress, they track work remaining across time. A burndown chart is a graphical representation of the amount of work left to do versus the time available. It helps the Scrum Team monitor and forecast the progress toward the Sprint Goal.
Question 72
What it the main reason for the Scrum Master to be at the Daily Scrum?
Options:
A.
To gather status and progress information to report to management.
B.
To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.
C.
He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.
D.
To make sure every team member answers the three questions.
Answer:
C
Explanation:
The correct answer is C, because the Scrum Guide states that “the Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.” Therefore, the main reason for the Scrum Master to be at the Daily Scrum is to ensure that it happens, but he or she does not have to be there.