Scrum PSM II Practice Test - Questions Answers, Page 4

Coach the Product Owner that achieving the Sprint Goal is the Scrum Team's objective. A forecast is only used to initially estimate the effort required to reach the Sprint Goal.

This is true because the Scrum Master's role is to help the Product Owner understand the Scrum framework and its principles, such as empiricism, self-organization, and collaboration12.The Scrum Master should also remind the Product Owner that the forecast is not a commitment, but a plan that can be adjusted based on the Sprint progress and feedback3. The Scrum Master should focus on the value and outcome of the Sprint, rather than the output and scope.

A) You suggest taking the person aside and asking them what they believe the key outcomes are for the Daily Scrum. Effectively coaching them to help create focus during the Daily Scrum.

This is a good suggestion because it shows respect and empathy for the person, while also helping them understand the purpose and value of the Daily Scrum.Coaching is one of the core competencies of a Scrum Master, and it can help the person self-reflect and improve their behavior12. E. You suggest coaching the Developers to help them find a way to solve the problem, and own the solution.

This is another good suggestion because it empowers the Developers to take ownership of their own process and communication.The Scrum Master's role is not to impose rules or solutions, but to facilitate and enable the team's self-organization and collaboration12. By coaching the Developers, the Scrum Master can help them address the issue in a constructive and respectful way.

This is a good option because the Scrum Master's role is to help the Scrum Team understand and apply the Scrum framework and its principles12.The Scrum Master should also facilitate and enable the team's self-organization and collaboration12.By coaching the Scrum Team, the Scrum Master can help them realize that the Daily Scrum is not a status update or a performance review, but a time to inspect and adapt their progress toward the Sprint Goal3. D. Tell the Product Owner your concerns about how his behavior may impact the Developers, and ask him to stop attending the Daily Scrum for some time.

This is another good option because the Scrum Master's role is to protect the Scrum Team from external interference and distractions12.The Scrum Master should also coach the Product Owner on how to maximize the value of the product and collaborate effectively with the Developers12. By telling the Product Owner your concerns, you can help him understand that his behavior may create pressure, dependency, or resentment among the Developers, which can harm their motivation, creativity, and autonomy . By asking him to stop attending the Daily Scrum for some time, you can give the Developers some space to self-manage their work and communication.

Using Scrum does not ensure that adding more resources to a project proportionally increases the value delivered.In fact, adding more resources may have the opposite effect, as it can introduce more complexity, communication overhead, coordination challenges, and integration issues12.Scrum values quality over quantity, and focuses on delivering the most valuable and feasible outcomes in a given timebox3.Scrum also encourages teams to be self-organizing and cross-functional, which means that they can work autonomously and collaboratively without relying on external resources or dependencies3.

This is the best answer because it is consistent with the Scrum values ofcommitment, courage, focus, openness, and respect12.By providing boundaries, such as the product vision, the product backlog, the budget, and the timeline, the organization can enable the team members to self-organize and form cross-functional and collaborative Scrum Teams3.This way, the team members can commit to their own goals, have the courage to face challenges, focus on delivering value, be open to feedback and learning, and respect each other's skills and perspectives12.

C) 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.

This is a good way because it is consistent with the Scrum principle ofempiricism, which means that the Scrum Team learns and adapts based on the actual outcomes and feedback, rather than following a predefined plan12. By adding these security concerns to the Product Backlog, the Product Owner can prioritize and refine them according to the value and urgency, and communicate them to the stakeholders.By addressing them throughout the next Sprints, the Scrum Team can deliver valuable and functional increments that also meet the security requirements34. 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

This is another good way because it is consistent with the Scrum value ofopenness, which means that the Scrum Team and the stakeholders have a clear and common understanding of the product vision, goals, progress, and risks12. By adding these expectations to the Definition of Done, the Scrum Team can ensure that every future Increment meets the quality standards and satisfies the stakeholder needs.By working with external specialists, the Scrum Team can also leverage their expertise and experience to better understand and implement the security requirements34.

Splitting a team into two teams is a major decision that should not be taken lightly. It may have implications for the product vision, the product backlog, the sprint goal, the sprint backlog, the definition of done, and the team dynamics. It may also reduce the effectiveness of the Scrum Team by creating dependencies, communication overhead, and coordination challenges. Therefore, before considering such a drastic measure, it is advisable to explore other options to improve the quality and efficiency of the Daily Scrum. One option is to ask for help from another Scrum Master who can observe the Daily Scrum and provide feedback and suggestions.

The Scrum Guide, section 3.2 (The Daily Scrum), page 9

The Scrum Master Learning Path, module 4 (The Daily Scrum), lesson 4 (Common Challenges) and lesson 5 (Tips for an Effective Daily Scrum)

The Scrum Guide states that ''the moment a Product Backlog item meets the Definition of Done, an Increment is born'' and that ''the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints''. Therefore, to deliver a product Increment that is integrated and potentially releasable, all Scrum Teams must have a shared understanding of what ''Done'' means and ensure that their work meets that standard. This also enables transparency, inspection, and adaptation across the Scrum Teams.

The Scrum Guide, section 3.4 (The Increment), page 10

The Scrum Master Learning Path, module 5 (The Increment), lesson 1 (What is an Increment?) and lesson 2 (Definition of Done)

The Scrum Value of openness can easily impact all of the aspects listed in the question. Openness means that the Scrum Team and the stakeholders agree to be transparent about their work, their challenges, their learnings, and their progress. This fosters a culture of collaboration, trust, feedback, and continuous improvement. Openness also helps to ensure that the product quality meets the expectations of the customers and the stakeholders, and that the product is delivered in a timely manner. Openness also contributes to employee satisfaction, as it allows the Scrum Team members to express their opinions, share their ideas, and learn from each other.

The Scrum Guide, section 2.2 (Scrum Values), page 6

The Scrum Master Learning Path, module 1 (Scrum Theory), lesson 3 (Scrum Values)