View Full Scrum PSM I Exam Dumps and Practice Test Dumps.

 

Question 221

What does Scrum require from every Increment?

1. A separate stakeholder contract
2. Compliance with the Definition of Done
3. Approval from senior management
4. Completion of all Product Backlog items

Correct Answer: 2

Explanation:

Every Increment must meet the Definition of Done to be considered a usable product result. The Definition of Done establishes the quality standard that completed work must satisfy. An Increment does not need approval from senior management, completion of every Product Backlog item, or a separate stakeholder contract. Scrum focuses on creating usable value incrementally rather than waiting until all possible product work is finished. Meeting the Definition of Done also supports transparency because everyone can distinguish completed product work from items that still require additional development.

Question 222

Which Scrum value encourages dedication to important objectives?

1. Commitment
2. Respect
3. Openness
4. Courage

Correct Answer: 1

Explanation:

Commitment is one of the five Scrum values and supports dedication to achieving meaningful goals. Scrum Teams demonstrate commitment through their focus on objectives such as the Product Goal and Sprint Goal while maintaining the quality represented by the Definition of Done. Commitment does not mean refusing to adapt. Developers can change their detailed plan when new information appears while continuing to pursue the Sprint Goal. Respect, Openness, Courage, and Focus are equally important Scrum values, but Commitment specifically emphasizes dedication to achieving the team’s objectives.

Question 223

What happens when the Sprint Goal becomes obsolete?

1. Developers extend the Sprint indefinitely
2. Stakeholders automatically cancel it
3. The Product Owner may cancel the Sprint
4. The Scrum Master becomes Product Owner

Correct Answer: 3

Explanation:

The Product Owner may cancel a Sprint when the Sprint Goal becomes obsolete. This authority belongs specifically to the Product Owner because the decision concerns whether the Sprint still has meaningful product value. Developers and stakeholders may provide information that helps identify the situation, and the Scrum Master can help everyone understand Scrum’s process, but they do not own the cancellation decision. Cancellation should not be used simply because the Sprint becomes difficult. The key condition is that its objective is no longer valuable or relevant to the product.

Question 224

Which artifact provides transparency about upcoming product work?

1. Sprint Goal
2. Increment
3. Definition of Done
4. Product Backlog

Correct Answer: 4

Explanation:

The Product Backlog provides transparency into the product work that may be needed in the future. It is an emergent and ordered list that changes as the Scrum Team learns more about the product and its environment. The Sprint Goal focuses on the current Sprint, the Increment represents completed usable product results, and the Definition of Done describes the quality standard for completed work. Product Backlog transparency helps the Product Owner and Scrum Team understand possible future work and supports informed ordering based on current knowledge about product value and opportunities.

Question 225

Who determines whether selected work fits the Sprint’s capacity?

1. Developers
2. Product Owner alone
3. Scrum Master alone
4. External customers

Correct Answer: 1

Explanation:

Developers determine how much selected work they can realistically take forward during a Sprint. They consider their understanding of the work, available capacity, technical complexity, and the Sprint Goal. The Product Owner contributes information about value and can clarify Product Backlog items, but does not unilaterally determine the Developers’ workload. The Scrum Master supports effective Scrum rather than assigning work. Customers can provide useful information but do not manage the team’s Sprint capacity. This approach supports self-management and encourages realistic Sprint planning.

Question 226

What does the Sprint provide a Scrum Team?

1. An unlimited development period
2. A fixed-length container for work
3. A permanent Product Backlog
4. A replacement for product strategy

Correct Answer: 2

Explanation:

The Sprint is a fixed-length container in which the Scrum Team works toward a Sprint Goal and creates a usable Increment. A Sprint lasts one month or less and begins immediately after the previous Sprint concludes. Its fixed duration creates a regular cadence for inspection and adaptation. The Sprint does not provide unlimited development time, replace product strategy, or make the Product Backlog permanent. Instead, it provides a bounded period in which the team can focus on a valuable objective while still responding to new information through appropriate adaptation.

Question 227

Which activity helps prepare Product Backlog items for future selection?

1. Sprint Retrospective
2. Daily Scrum
3. Product Backlog refinement
4. Sprint Review

Correct Answer: 3

Explanation:

Product Backlog refinement helps prepare items for future selection by adding useful detail, improving understanding, and adjusting order or size when appropriate. Refinement is an ongoing activity rather than a separate formal Scrum event. It can happen whenever the Scrum Team needs to improve its understanding of upcoming work. The Daily Scrum focuses on current Sprint progress, the Sprint Review inspects the product outcome, and the Sprint Retrospective examines team effectiveness. Refinement therefore supports future planning by making relevant Product Backlog items sufficiently understood at the appropriate time.

Question 228

What is the main focus of Developers during the Sprint?

1. Maximizing shareholder dividends
2. Managing company recruitment
3. Rewriting organizational policies
4. Creating a usable Increment

Correct Answer: 4

Explanation:

Developers are accountable for creating a usable Increment each Sprint. Their work includes creating the Sprint plan, maintaining the Sprint Backlog, adapting their approach, and ensuring that completed work meets the Definition of Done. They do not become responsible for organizational recruitment, shareholder dividends, or company-wide policy management. Their focus remains on transforming selected Product Backlog work into product value. By maintaining attention on the Sprint Goal and usable Increment, Developers help the Scrum Team make tangible progress toward the Product Goal.

Question 229

What does the Product Owner consider when evaluating product value?

1. Relevant evidence and stakeholder needs
2. Only the number of completed meetings
3. Developer preferences alone
4. Historical estimates without new information

Correct Answer: 1

Explanation:

The Product Owner considers relevant evidence when making product decisions, including stakeholder needs, product outcomes, market information, risks, opportunities, and new learning. Product value cannot reliably be determined by meeting counts or outdated estimates alone. Developers provide important technical information, but product-value decisions are not based exclusively on Developer preferences. Because complex product development produces new information, the Product Owner may revise priorities as understanding improves. This supports effective Product Backlog management and helps direct the Scrum Team toward work that can provide meaningful product value.

Question 230

Which event gives the Scrum Team an opportunity to examine its process?

1. Sprint Review
2. Sprint Retrospective
3. Sprint Planning
4. Daily Scrum

Correct Answer: 2

Explanation:

The Sprint Retrospective provides the Scrum Team with an opportunity to examine how it worked during the Sprint. The team considers people, interactions, processes, tools, and the Definition of Done, then identifies useful improvements. The Sprint Review focuses primarily on the product outcome and future direction, while Sprint Planning establishes the next Sprint’s objective and initial plan. The Daily Scrum focuses on progress toward the Sprint Goal. The Retrospective therefore provides dedicated space for improving the team’s effectiveness rather than focusing primarily on product scope.

Question 231

What does the Product Owner remain accountable for after delegation?

1. Developer task assignment
2. Technical architecture
3. Product Backlog management
4. Sprint event facilitation

Correct Answer: 3

Explanation:

The Product Owner can delegate activities related to Product Backlog management but remains accountable for the effectiveness of that management. Delegation does not remove the Product Owner’s accountability. The Product Owner remains responsible for ensuring that the Product Goal and Product Backlog are effectively managed and communicated. Developers remain accountable for creating the Increment and managing their Sprint work, while the Scrum Master supports Scrum effectiveness. This distinction allows practical activities to be shared without creating uncertainty about who ultimately owns the Product Owner accountability.

Question 232

Why must Scrum artifacts be transparent?

1. To support meaningful inspection
2. To prevent adaptation
3. To guarantee identical Sprints
4. To eliminate stakeholder feedback

Correct Answer: 1

Explanation:

Transparency allows Scrum artifacts to be understood well enough for meaningful inspection. If important information about the product, current Sprint work, or quality standard is hidden or misunderstood, inspection may lead to unreliable conclusions. Transparency therefore supports the empirical nature of Scrum. It does not prevent adaptation or eliminate stakeholder feedback. Instead, transparent artifacts help the Scrum Team and stakeholders understand the current situation and decide whether changes are appropriate. Product Backlog, Sprint Backlog, and Increment transparency all contribute to better-informed decisions throughout product development.

Question 233

What does the Sprint Goal give Developers when scope changes?

1. A reason to stop the Sprint
2. A fixed technical solution
3. A continuing objective to protect
4. Permission to ignore product value

Correct Answer: 3

Explanation:

The Sprint Goal provides Developers with a continuing objective that remains important even when details of the Sprint work change. Scope can be clarified or renegotiated with the Product Owner when new information appears, provided the Sprint Goal remains intact. This gives Developers flexibility without losing the purpose of the Sprint. The Sprint Goal does not prescribe a technical solution or allow the team to ignore product value. If the objective itself becomes obsolete, the Product Owner may cancel the Sprint. Otherwise, the team adapts its plan around the goal.

Question 234

Which statement best describes Scrum’s events?

1. They are optional status meetings
2. They create regular opportunities for inspection and adaptation
3. They replace Product Backlog management
4. They eliminate the need for collaboration

Correct Answer: 2

Explanation:

Scrum events are designed to create regular opportunities for inspection and adaptation. Each event has a specific purpose that contributes to empirical product development. Sprint Planning establishes the Sprint objective and plan, the Daily Scrum supports daily inspection and adaptation, the Sprint Review examines the product outcome and future direction, and the Sprint Retrospective improves team effectiveness. These events are not merely status meetings and do not replace Product Backlog management. Collaboration remains important throughout Scrum, and the events provide structured opportunities for people to work together around specific purposes.

Question 235

What should happen when an Increment does not meet the Definition of Done?

1. It should be considered incomplete
2. It becomes a separate Product Goal
3. It is automatically released
4. It replaces the Sprint Goal

Correct Answer: 1

Explanation:

An Increment must meet the Definition of Done to be considered complete and usable. If work does not satisfy the Definition of Done, it remains incomplete and cannot be represented as part of the completed Increment. The team may continue working on it later if it remains valuable, but its unfinished status should remain transparent. It does not automatically become a Product Goal, replace the Sprint Goal, or qualify for release merely because development effort has been spent. The Definition of Done therefore protects the quality and transparency of product results.

Question 236

Which Scrum pillar enables decisions to respond to inspection results?

1. Transparency
2. Adaptation
3. Commitment
4. Focus

Correct Answer: 2

Explanation:

Adaptation is the Scrum pillar that enables the team to change its approach when inspection reveals that an adjustment is needed. Transparency makes relevant information visible, inspection examines that information, and adaptation responds to what has been learned. Commitment and Focus are Scrum values rather than pillars of empiricism. Adaptation does not mean changing plans without evidence. Effective adaptation should be based on meaningful inspection and should occur soon enough to prevent further problems or unnecessary work. This relationship between transparency, inspection, and adaptation is central to Scrum’s empirical approach.

Question 237

What does self-management prevent within a Scrum Team?

1. Developers choosing how to organize their work
2. Shared responsibility for Sprint outcomes
3. A manager assigning every technical task
4. Collaboration among team members

Correct Answer: 3

Explanation:

Self-management means the Scrum Team internally decides who does what, when, and how. This prevents the need for an external manager to assign every technical task to individual Developers. Developers collectively organize their work and adapt their plan as circumstances change. Self-management does not eliminate collaboration or shared accountability. Instead, it strengthens the team’s ability to use its combined skills effectively. The Scrum Master supports self-management through coaching and facilitation rather than becoming a task manager. This structure encourages ownership and responsiveness during complex product development.

Question 238

What does the Sprint Review use to support future decisions?

1. Actual product results and relevant information
2. Employee attendance statistics
3. Unrelated departmental budgets
4. Personal assumptions without inspection

Correct Answer: 1

Explanation:

The Sprint Review uses the actual Sprint outcome and relevant information from stakeholders and the product environment to support future decisions. Inspecting the Increment gives participants evidence about what has actually been achieved. Stakeholder feedback, market changes, and other environmental information can then help shape discussions about what to consider next. Employee attendance statistics or unrelated budgets are not the central basis for product decisions during this event. The Review therefore connects actual product evidence with collaborative discussion about future Product Backlog direction and potential adaptations.

Question 239

Which commitment helps clarify the objective of the current Sprint?

1. Product Goal
2. Definition of Done
3. Sprint Goal
4. Product Backlog

Correct Answer: 3

Explanation:

The Sprint Goal is the commitment associated with the Sprint Backlog and provides the objective for the current Sprint. It explains why the Sprint is valuable and gives Developers a shared purpose for the selected work. The Product Goal provides longer-term product direction, while the Definition of Done establishes the quality standard for completed work. The Product Backlog contains the ordered work that may contribute to the product. Keeping these concepts distinct helps the Scrum Team understand how short-term Sprint objectives connect with longer-term product development.

Question 240

What happens immediately when one Sprint concludes?

1. Product development permanently stops
2. The next Sprint begins
3. The Product Backlog is deleted
4. Scrum accountabilities are reassigned

Correct Answer: 2

Explanation:

The next Sprint begins immediately after the previous Sprint concludes. Scrum uses consecutive fixed-length Sprints to create a continuous cadence for inspection, adaptation, and delivery of usable Increments. The end of one Sprint does not automatically stop product development, delete the Product Backlog, or reassign Scrum accountabilities. Instead, the Scrum Team continues working toward its Product Goal through the next Sprint. Sprint Planning occurs as part of the new Sprint and establishes its objective and initial plan. This continuous rhythm helps maintain regular opportunities for learning and product improvement.