How should requirements be distributed when multiple Scrum Teams work on the same product?
(choose the best answer)
A. The Scrum Team with the highest velocity pulls items from an overall Product Backlog first.
B. They must be selected from one Product Backlog in such a way that each Scrum Team has an equal volume of requirements per Sprint.
C. The Product Owner decides by providing each team with its own Product Backlog.
D. The Developers pull in work from a shared Product Backlog in agreement with the Product Owner and the other teams.

Which of the following affect the outcome of a Sprint?
(choose all that apply)
A. The skills and working relationships of the people on the Scrum Team(s).
B. The stability and complexity of the technology.
C. The complexity of the requirements.

Which statement about the Sprint Goal is incorrect?
(choose the best answer)
A. It is only a forecast and may change within the Sprint as more is learned.
B. If it doesn’t seem achievable, the Developers have the courage to tell the Product Owner.
C. The Product Owner respects the opinions of the Developers about whether they can achieve the Sprint Goal.
D. It helps increase focus.
E. The Scrum Team discusses openly about alternative ways to reach it.
F. The Scrum Team commits to it.

At a Sprint Review meeting, the Product Owner introduces the functionality that is likely to be done over the next Sprints. The Chief Security Officer reminds everyone that through the envisioned functionality, sensitive personal user data will be stored. This might be the subject of external security audits. He reminds everyone of the important non-functional requirements with regards to security. These were not applicable and not considered previously.
What are two good ways the Scrum Team can handle these high-security concerns?
(choose the best two answers)
A. They are discussed, determined, and documented in parallel Sprints to not disturb the actual feature development. Once analyzed, they should be applied to the work already done before further feature development can continue.
B. They should be handled by a separate, specialist team in a parallel Sprint so they can be specifically resolved through an improved application design without hindering functional development.
C. The impact of these security concerns on past AND future work needs to be determined before new Sprints can start. A list of security-related Product Backlog items needs to be passed on to the Product Owner before starting the next Sprint.
D. During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements.
E. They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.

You are a Scrum Master employed by the IT department. The IT manager considers adopting Scrum for a new project. He wonders however what the value is in having all team members attend this meeting called “Daily Scrum” every day. The organization already has its employees attending so many mandatory meetings.
What are two outcomes of the Daily Scrum you inform him about, to express the importance of the Daily Scrum?
(choose the best two answers)
A. During the Daily Scrum the Developers will bring up problems that are hindering their progress, and for which they have no means to resolve. They will inform you as a Scrum Master, so you can take care of them and help the team be more productive.
B. Through the short, daily alignment of the Daily Scrum the Developers grow and improve a shared understanding of the most important work to be undertaken next, in the next 24 hours, to achieve the best possible progress toward the Sprint Goal. This daily opportunity to inspect and adapt will enable the Developers to best tackle any unforeseen circumstances that might otherwise disrupt the team’s progress.
C. The Developers will produce a status report indicating what each individual has done the past working day, and how much time that has taken. The accumulated reports will support discussing how the Sprint went at the Sprint Review meeting. It will provide detailed insights into the accuracy of estimates versus actual time spent, which can be used to create better estimates at the subsequent Sprint Planning meeting.
D. The Daily Scrum serves for the Developers to report to you, as a Scrum Master, all updates on the tasks for the Sprint, as registered in the Sprint Backlog. You can then use the Developers’ updates to plan their work for the next day, making sure that every member is assigned the right tasks.
E. During the Daily Scrum, the Developers need to update the Scrum board with their current status and progress, at a task level. This is crucial to ensure that the IT manager can go up to the room at any possible time and control the team’s actual progress.

User documentation is part of the Definition of Done. However, there are not enough technical writers to go around. Your Scrum Team does not have a Technical Writer. What needs to be done?
(choose the best answer)
A. You Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
B. Let the user documentation remain undone and accumulate until after the last development Sprint. It will be then done by any available technical writers.
C. Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.