Scrum PSM-II Exam Questions

The best two answers are A and C.

A) Timeboxing work to allow for frequent inspection. This is a relevant boundary for self-management provided by the Scrum framework, as it helps the Scrum Team to organize their work into fixed-length Sprints and other events, such as the Daily Scrum, the Sprint Planning, the Sprint Review, and the Sprint Retrospective. Timeboxing enables the Scrum Team to inspect their progress, adapt their plan, and deliver value regularly and predictably.

C) Creating a valuable and useful Increment by the end of each Sprint. This is also a relevant boundary for self-management provided by the Scrum framework, as it guides the Scrum Team to focus on delivering a product Increment that meets the Sprint Goal and the Definition of Done. Creating a valuable and useful Increment requires the Scrum Team to collaborate, communicate, and coordinate effectively, and to apply their skills and creativity to solve complex problems.

The Scrum Guide, section 2.3 (The Scrum Team), page 7

The Scrum Guide, section 3.1 (The Sprint), page 8

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

The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 2 (The Sprint), lesson 3 (The Sprint Goal), lesson 4 (Sprint Planning) and lesson 5 (The Sprint Review)

The Professional Scrum Master II (PSM II) Assessment, question 40

The best way to determine if the Product Owner is interacting with the Developers enough throughout a Sprint is to observe whether both parties are satisfied with the Increment.The Increment is a concrete stepping stone toward the Product Goal1.It must be usable and meet the Definition of Done1.The Product Owner is accountable for maximizing the value of the product resulting from the work of the Developers1.The Developers are accountable for creating a valuable, useful, and potentially releasable Increment every Sprint1. Therefore, if both the Product Owner and the Developers are happy with the quality and value of the Increment, it means that they have communicated and collaborated effectively throughout the Sprint.

Some reasons why the other options are not correct are:

A: The Developers should determine the percentage of time the Product Owner is required to be present and monitor whether the Product Owner's average presence is around this figure. This option is not correct because it implies that there is a fixed or optimal amount of time that the Product Owner should spend with the Developers, which may not be true. The Product Owner's interaction with the Developers may vary depending on the context, complexity, and uncertainty of the product and the Sprint.The Scrum Guide does not prescribe any specific time or frequency for the Product Owner's involvement with the Developers1.The Product Owner should be available to provide guidance and feedback to the Developers as needed, but not interfere with their self-organization and autonomy1.

B: Check the Daily Scrum reports to see whether the Product Owner was present at the majority of the Daily Scrum meetings. This option is not correct because it assumes that the Daily Scrum is a meeting where the Product Owner should be present, which is not true.The Daily Scrum is an event for and by the Developers12, not for reporting or accountability to anyone else.The Product Owner may attend as an observer or a collaborator, but only if invited by the Developers12. The presence or absence of the Product Owner at the Daily Scrum does not indicate how much they interact with the Developers throughout the Sprint.

C: Observe whether the Developers need to ask the Product Owner questions at times other than during the Daily Scrum. This option is not correct because it implies that asking questions is a sign of insufficient interaction, which may not be true. Asking questions is a natural and healthy part of communication and collaboration between the Product Owner and the Developers. It shows that they are engaged, curious, and willing to learn from each other. It also helps them to clarify requirements, expectations, and feedback, and to resolve any ambiguities or conflicts. Asking questions does not necessarily mean that there is a lack of interaction, but rather that there is a need for more information or clarification.

What is an Increment? | Scrum.org

What Is a Daily Standup? | A Guide to Running Effective Standup Meetings | Atlassian

C) Timeboxes encourage the people who are closest to the problem to create the best possible result in the time allotted, given the current context.

This is true because timeboxes limit the amount of time that can be spent on an activity, which forces the Scrum Team to focus on the most valuable and feasible outcomes.Timeboxes also empower the Scrum Team to make decisions based on their own expertise and experience, rather than relying on external authorities or instructions12. D. Timeboxes help everyone focus on the same problem at the same time.

This is true because timeboxes create a shared sense of urgency and alignment among the Scrum Team and the stakeholders.Timeboxes also enable frequent feedback and inspection, which help the Scrum Team adapt to changing requirements and expectations12.

This is the best answer because it empowers the Developers to take ownership of their own process and find a solution that works for them. The Scrum Master can facilitate the discussion and help the Developers understand the value and importance of the Daily Scrum, but not impose or dictate any specific action or rule. The Scrum Master can also support the Developers in conducting an experiment and evaluating the results, if they decide to do so.

Scrum Guide 2020, page 13: ''The Scrum Master serves the Scrum Team in several ways, including coaching the team members in self-management and cross-functionality.''

Professional Scrum Master II Course, page 14: ''The Daily Scrum is a key opportunity for inspection and adaptation at the team level. It helps the team to synchronize their work, identify impediments, and collaborate on solutions.''

Professional Scrum Master II Course, page 21: ''The Scrum Master can help the team to resolve conflicts by facilitating dialogue, listening actively, asking powerful questions, and supporting collaborative decision making.''

During the Sprint Review of a scaled development effort, the Scrum Teams should demonstrate the integrated Increment that they have collectively delivered, not their individual Increments separately. This ensures that the stakeholders can provide feedback on the value and quality of the product as a whole, and that the Scrum Teams can inspect their alignment and collaboration.

Scrum Guide 2020, page 14: ''The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.''

Nexus Guide 2020, page 7: ''The Nexus Sprint Review is an event where appropriate stakeholders review the Integrated Increment that has been built throughout the Sprint by all Scrum Teams in a Nexus.''