Please select 2 correct answers
Explanation:
Only the Development Team can change its Sprint Backlog during a Sprint. If the Product Owner
wants to change the work planned, he has to do this in accordance with the Development Team.
Explanation:
This is not prohibited by the Scrum Guide. It can be hard to wear "two hats". It can be difficult to fully attend to
all expectations of the Scrum Master role, while also being a focused Developer. It can be helpful to understand
more of Development work. It can also be a pitfall.
Please select 2 correct answers
Explanation:
A) By elimination, this one must be the third true statement. Why? Well: "Only the Product Owner has the authority to cancel the Sprint".
In the end it's at the PO's discretion. In 99.9% of the cases it would be good to share the reason, and really bad for transparency, trust,
morale to not do so. However, he/she can do it. For what reason? Maybe they are a horrible person, bad at their job. Or maybe the company
got acquired by some other party, making the Sprint Goal obsolete, but the Product Owner is under a Non Disclosure Agreement to not tell
the teams about it. Who knows? In short: it would almost always be bad, but there's nothing in the Scrum Guide specifically preventing it. True.
B) Is in the Scrum Guide, pretty obvious one. True.
C) A sprint can be cancelled until the time box is over, not when it is over. False.
D) The term "pressure" is there to scare you, but the Scrum Guide states he can "influence the decision" to cancel. He can't force,
but he can apply some pressure if he/she deems it necessary. So, True.
E) Not all work is typically put back on the Product Backlog, and specifically not in the mandatory way this answer puts it. Per the
Scrum Guide: "When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. If part of the work is
potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back
on the Product Backlog." So, False.
Please select 2 correct answers
Explanation:
This is running out of hand, core Scrum Values such as respect are being forgotten. The Scrum Master needs to act.
A natural conclusion is therefore not the best answer. Having the Product Owner choose how the work is done is not
ok. The developers decide how. They work with the Product Owner to decide upon scope, but the Product Owner
should not choose the technical approach as stated here.
Please select 2 correct answers
Explanation:
Not being transparent about uncertainty is unethical. Endangering customers' privacy is unethical. Go see this excellent
Scrum.org video.. The development team owns the Sprint Backlog, they can have good reasons to refuse work. A Product
Owner is free to order the Product Backlog how he wants. If a team wants to use additional tools to improve their process,
that's usually to be encouraged. In any case, it's not a breach of ethics.
Explanation:
Yes, this should be addressed by the Scrum Master if the team appears unable to do so. A careful approach is needed.
Please select 3 correct answers
Explanation:
The wrong answers are listed in the Scrum Guide as Product Owner activities.
Explanation:
The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that
they do not disrupt the meeting. However, if the Product Owner is present and the team requests him to give valuable
input, this is allowed. Disruption is not the same as interaction.
Please select 2 correct answers
Explanation:
Scrum Guide: The Scrum Team decides how and when refinement is done. Refinement usually consumes no more
than 10% of the capacity of the Development Team.
Explanation:
The Nexus Integration Team is accountable for ensuring that a “Done” Integrated Increment
(the combined work completed by a Nexus) is produced at least once every Sprint.
Explanation:
Scrum Guide: The Daily Scrum is an internal meeting for the Development Team. If others are
present, the Scrum Master ensures that they do not disrupt the meeting.
Explanation:
People personally commit to achieving the goals of the Scrum Team. The Scrum Team members have courage
to do the right thing and work on tough problems.
Explanation:
All are good options. Teach in a friendly, compassionate tone. Address during the retrospective when it seems
that tensions still surround this subject.
Please select 2 correct answers
Explanation:
It is the Product Owner's responsibility, but he/she is aware of this. Pointing that out again is not helpful advice.
Management is unlikely to know end-users their exact wishes and expectations.
Please select 3 correct answers
Explanation:
Scrum Guide: although implementing only parts of Scrum is possible, the result is not Scrum.
Please select 3 correct answers
The Correct Answers are A The Increment, E The Sprint Backlog, and F The Product Backlog
Please select 2 correct answers
Explanation:
Scrum Guide: Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect
undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work.
The Daily Scrum is for the development team to synchronize, no-one else participates. Interaction and inspection
should not be limited, it should be regular and effective.
Please select 3 correct answers
Explanation:
Velocity can be a helpful tool for teams. It is unsuitable to draw comparisons, depends on estimation, and tracks output,
which does not equate succesful outcome. It can be used to spark conversations within the team and self-inspect.
Please select 2 correct answers
Explanation:
This is running out of hand, core Scrum Values such as respect are being forgotten. The Scrum Master needs to act
A natural conclusion is therefore not the best answer. Having the Product Owner choose how the work is done is not
ok. The developers decide how. They work with the Product Owner to decide upon scope, but the Product Owner should
not choose the technical approach as stated here.
Please select 2 correct answers
Explanation:
The lack of transparency is best served by joining inspection during Sprint Review. As a stakeholder, the CEO
should work with the Product Owner to make his expectations known.
Explanation:
Forecast implies uncertainties, a prediction based upon what's known at this point. Specifically: not a commitment.
Explanation:
Product Backlog management includes: [...] - Optimizing the value of the work the Development Team performs; [...]
The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains
accountable.
Please select 2 correct answers
Explanation:
Scrum guide: "Scrum prescribes four formal events for inspection and adaptation [...] Sprint Planning,
Daily Scrum, Sprint Review, Sprint Retrospective"
Explanation:
The Sprint Goal should always be first in mind. The other subjects are secondary and viewed through the lens
of "how does this impact the Sprint Goal?".
Explnation:
Though a few of these answers are somewhat right, not all are directly related to Scrum being a framework.
From the Scrum Guide: "Scrum is not a process, technique, or definitive method. Rather, it is a framework within
which you can employ various processes and techniques."
