Towards the end of the Sprint Planning meeting, the Product Owner and the Developers have not been able to reach a clear, mutual understanding about the highest order Product Backlog items. Because of this, the Developers could not figure out how many Product Backlog items they could forecast for the upcoming Sprint. The Product Owner did make clear what business objective he is hoping to achieve with this Sprint. Which of the following two actions would you support?
(choose the best two answers)
A. The Developers forecast the most likely Product Backlog items to meet the business objective and create a Sprint Backlog based on a likely initial design and plan. Once the timebox for the Sprint Planning event is over, they start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.
B. If all agree they can continue the Sprint Planning meeting as a team past its timebox, until an adequate number of Product Backlog items are well enough understood for the Developers to make a complete forecast. Then start the Sprint.
C. The team splits up and everybody takes as much time as they need to study the Product Backlog items first. The Product Owner should be available to answer individual questions. The group reconvenes when all team members are better prepared and restart the Sprint Planning meeting before the Sprint can start.
D. They discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

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.

At the seventh Sprint Review, the stakeholders seem disappointed and angry. When asked about it, they say the product being built will not meet their needs and will cost more than they anticipated spending. What factors may have led to this?
(choose the best three answers)
A. The Product Owner has not been interacting frequently with the stakeholders and kept them aware of the progress of the project.
B. The stakeholders haven’t been using the Sprint Reviews to actively engage, and inspect and evaluate progress.
C. Changes to the project plan were not adequately documented and shared. The change request procedure was not diligently followed.
D. The stakeholders were not allowed to enter the development area, or be present at the Daily Scrum.
E. The Scrum Master has not ensured transparency.
F. The Project Management Office (PMO) and its project managers have not been engaged adequately causing the project plan to become inaccurate.

In Sprint Planning, the Developers work with the Product Owner to create a forecast for the Sprint. A forecast is a selection of Product Backlog items that the Developers deem feasible to get done by the end of the Sprint. Select two things that explain what “Done” means.
(choose the best two answers)
A. All work to create an Increment of software that is ready for acceptance testing by the Product Owner.
B. All work to create an Increment of software that is ready for integration testing.
C. Having an Increment of software that could be released to end users.
D. All work performed as listed in the Definition of Done.
E. All work for which enough expertise and skills are actually present in the Scrum Team.

What is the way to determine if the Product Owner is interacting with the Developers enough throughout a Sprint?
(choose the best answer)
A. Check the Daily Scrum reports to see whether the Product Owner was present at the majority of the Daily Scrum meetings.
B. Observe whether the Product Owner is satisfied with the Increment at the Sprint Review.
C. Observe whether the Developers need to ask the Product Owner questions at times other than during the Daily Scrum.
D. Determine the percentage of time the Product Owner is required to be present with the Developers. Control whether the Product Owner’s average presence is around this figure.

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.