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

Question 281

What is the Product Owner accountable for communicating clearly?

1. Product Goal
2. Daily Scrum format
3. Developer assignments
4. Retrospective agenda

Correct Answer: 1

Explanation:

The Product Owner is accountable for developing and explicitly communicating the Product Goal. The Product Goal describes a future state of the product and provides a long-term objective for the Scrum Team. The Product Owner is also accountable for effective Product Backlog management, including clearly communicating Product Backlog items and ensuring the Product Backlog is transparent and understood. The Product Owner does not determine the Daily Scrum format or assign individual technical tasks to Developers. Clear communication of the Product Goal helps the Scrum Team understand the broader direction behind its product-development work.

Question 282

Which Scrum event allows stakeholders to collaborate on future product direction?

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

Correct Answer: 2

Explanation:

The Sprint Review provides an opportunity for the Scrum Team and stakeholders to inspect the Sprint outcome and collaborate on what to do next. Relevant information about the product and its environment can influence future decisions. Stakeholders may provide feedback, domain knowledge, market information, or other useful insights. The event is not simply a presentation of completed work. It is a working session focused on inspection and adaptation. Developers, the Product Owner, and stakeholders can use the information discussed during the Review to develop a shared understanding of possible future Product Backlog adjustments and product direction.

Question 283

Which Scrum principle helps teams respond to complex uncertainty?

1. Detailed long-term prediction
2. Centralized task assignment
3. Empirical process control
4. Fixed technical implementation

Correct Answer: 3

Explanation:

Scrum uses empiricism to address complex work where the future cannot be predicted with complete certainty. Empiricism relies on transparency, inspection, and adaptation. Relevant information is made visible, actual results are examined, and the approach is adjusted when necessary. This allows the Scrum Team to learn from experience instead of depending entirely on assumptions established before development begins. Empiricism does not remove planning or structure. Instead, it recognizes that plans and decisions should be informed by what is observed. This approach is particularly useful when product requirements, technology, and environmental conditions can change.

Question 284

Who determines how much selected work can be accomplished during a Sprint?

1. Product Owner
2. Scrum Master
3. Stakeholders
4. Developers

Correct Answer: 4

Explanation:

Developers determine how much work they can accomplish during a Sprint. They create the plan for the Sprint and decide how the selected work can be transformed into a usable Increment. The Product Owner is accountable for Product Backlog management and value, but does not dictate how much work Developers must forecast. Developers consider the Sprint Goal, their understanding of the work, and relevant technical information when creating the Sprint Backlog. Their plan can change as more is learned. This reflects Scrum’s self-managing approach, where Developers determine how to accomplish the work rather than receiving detailed technical assignments from outside.

Question 285

What does the Scrum value Respect encourage among team members?

1. Recognizing each person’s capabilities and contributions
2. Avoiding all disagreements
3. Allowing managers to control technical choices
4. Prioritizing individual competition

Correct Answer: 1

Explanation:

Respect means that Scrum Team members respect each other as capable, independent people. Scrum relies on collaboration among professionals with different skills and perspectives. Respect helps create an environment where people can contribute their knowledge, challenge ideas constructively, and work toward shared objectives. Respect does not require eliminating disagreement; constructive disagreement can help teams inspect assumptions and improve decisions. It also does not establish a hierarchy in which managers control technical choices. Combined with Commitment, Focus, Openness, and Courage, Respect supports the collaborative environment needed for effective self-management and product development.

Question 286

What is included in the Sprint Backlog besides selected Product Backlog items?

1. Only stakeholder feedback
2. Sprint Goal and actionable plan
3. Product Owner’s annual strategy
4. Organizational budget

Correct Answer: 2

Explanation:

The Sprint Backlog consists of the Sprint Goal, selected Product Backlog items, and an actionable plan for delivering the Increment. The Sprint Goal provides the objective, the selected Product Backlog items represent the work chosen for the Sprint, and the plan describes how Developers intend to accomplish that work. Developers create and adapt the Sprint Backlog throughout the Sprint as more is learned. It is therefore a living plan rather than a document that remains unchanged. Stakeholder feedback and organizational information can influence decisions, but they are not required components of the Sprint Backlog.

Question 287

Which statement best describes an Increment?

1. It is only a collection of proposed features
2. It is a list of future Product Backlog items
3. It is a usable result meeting the Definition of Done
4. It is a temporary development estimate

Correct Answer: 3

Explanation:

An Increment is a concrete stepping stone toward the Product Goal. It must be usable and meet the Definition of Done. Each Increment is additive to previous Increments and must work with them. Scrum allows multiple Increments to be created within a Sprint, and an Increment can be delivered before the Sprint ends. Work cannot be considered part of an Increment unless it meets the Definition of Done. Therefore, proposed features, future Product Backlog items, and estimates are not Increments. The Increment represents an actual product result that can support inspection and provide value.

Question 288

What is the maximum timebox for Sprint Planning in a one-month Sprint?

1. Four hours
2. Six hours
3. Three hours
4. Eight hours

Correct Answer: 4

Explanation:

Sprint Planning has a maximum timebox of eight hours for a one-month Sprint. Shorter Sprints usually require less time for planning because there is less work and uncertainty to consider. Sprint Planning addresses why the Sprint is valuable, what can be accomplished, and how the chosen work will be done. The resulting Sprint Goal becomes the commitment for the Sprint Backlog. Developers then create an actionable plan. The eight-hour duration is a maximum timebox, not a requirement to use the entire period. The Scrum Team should spend only the necessary time within that limit.

Question 289

What is the Scrum Master’s role regarding impediments?

1. Help cause them to be removed
2. Assign them to stakeholders
3. Add them to the Product Goal
4. Ignore them until Retrospective

Correct Answer: 1

Explanation:

The Scrum Master helps cause impediments to be removed from the Scrum Team’s progress. The Scrum Master may coach the team to address an impediment itself, facilitate conversations, or work with people outside the team when organizational barriers exist. This does not mean the Scrum Master personally performs every removal action. The Scrum Master’s broader accountability is to establish Scrum and help the Scrum Team become more effective. An impediment does not need to wait for the Sprint Retrospective before being addressed. When an obstacle affects progress, appropriate action can be taken as soon as possible.

Question 290

What does the Product Backlog become as the product evolves?

1. A permanently fixed requirements document
2. An increasingly detailed and informed artifact
3. A completed historical record
4. A list controlled exclusively by Developers

Correct Answer: 2

Explanation:

The Product Backlog is emergent and evolves as more is learned about the product. Items can gain additional detail, be reordered, resized, split, or removed as understanding changes. Product Backlog refinement is an ongoing activity that helps improve the clarity and usefulness of future work. The Product Owner remains accountable for effective Product Backlog management, while Developers and stakeholders can provide important information. The backlog is therefore not a permanently fixed requirements document. Its evolving nature supports empirical product development because new evidence and changing circumstances can influence what work is considered valuable and when it should be pursued.

Question 291

Which Scrum value emphasizes maintaining attention on essential work?

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

Correct Answer: 3

Explanation:

Focus is one of the five Scrum values and encourages the Scrum Team to concentrate on the work and objectives that matter. During a Sprint, the Sprint Goal provides a central objective that helps Developers make decisions about their work. Focus does not mean refusing to respond to new information. Developers can adapt their plan when necessary while continuing to pursue the Sprint Goal. The other Scrum values also contribute to effective teamwork, but Focus specifically emphasizes concentration on important goals and work. Together, Commitment, Focus, Openness, Respect, and Courage support effective collaboration and empiricism.

Question 292

What happens immediately after one Sprint ends?

1. A mandatory planning holiday begins
2. The Product Backlog is frozen
3. Another Sprint begins
4. Stakeholders select the Developers

Correct Answer: 3

Explanation:

The next Sprint begins immediately after the previous Sprint ends. Scrum uses consecutive fixed-length Sprints to create a continuous rhythm of inspection, adaptation, and product development. There is no required gap between Sprints. Sprint Planning for the new Sprint establishes its objective and selected work, while the Scrum Team continues learning from previous results. The Product Backlog can continue evolving, and stakeholders do not select or replace Developers as part of the transition. Each new Sprint provides another opportunity to create a usable Increment and make progress toward the Product Goal.

Question 293

Why must an Increment satisfy the Definition of Done?

1. To ensure it meets the required quality measures
2. To make Sprint Planning unnecessary
3. To prevent all future changes
4. To eliminate stakeholder feedback

Correct Answer: 1

Explanation:

An Increment must satisfy the Definition of Done because the Definition of Done is the formal description of the state of the Increment when it meets the quality measures required for the product. It creates a shared understanding of completed work and supports transparency. If a Product Backlog item does not meet the Definition of Done, it cannot be considered part of the Increment. This requirement does not prevent future changes or eliminate stakeholder feedback. Instead, it ensures that work presented as part of an Increment has reached the Scrum Team’s established quality standard.

Question 294

What does the Sprint Goal provide when Sprint scope changes?

1. A fixed list of technical methods
2. A replacement for the Definition of Done
3. A shared objective for the Sprint
4. A permanent Product Backlog order

Correct Answer: 3

Explanation:

The Sprint Goal provides a shared objective that helps maintain direction when details of the Sprint scope change. During the Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned, provided the Sprint Goal remains valuable. This flexibility allows Developers to adapt without losing the purpose of the Sprint. The Sprint Goal does not prescribe technical methods, replace the Definition of Done, or permanently order the Product Backlog. It is the commitment associated with the Sprint Backlog and gives Developers a clear objective toward which their evolving plan can be directed.

Question 295

What does the Sprint Review inspect besides the Increment?

1. Only individual work hours
2. Only internal team conflicts
3. Changes in the product environment
4. Only the Scrum Master’s coaching notes

Correct Answer: 3

Explanation:

The Sprint Review considers the Increment along with relevant changes in the product environment. The environment can include market conditions, customer expectations, business circumstances, technology, regulations, or other information that may affect product decisions. The Scrum Team and stakeholders use this information to understand what has changed and discuss possible next steps. The Sprint Review is therefore more than a demonstration of completed work. It is a collaborative inspection and adaptation opportunity. Internal team improvement belongs more directly to the Sprint Retrospective, while individual work-hour tracking is not the primary purpose of the Review.

Question 296

Which Scrum value supports openly discussing problems?

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

Correct Answer: 4

Explanation:

Openness is a Scrum value that encourages the Scrum Team and stakeholders to be open about the work and the challenges involved. Product development contains uncertainty, and hiding problems can prevent meaningful inspection and adaptation. Openness helps make relevant information visible so the team can respond appropriately. It works alongside Courage, which supports addressing difficult issues, and Respect, which supports constructive collaboration. Openness does not mean that every conversation must be public or unrestricted. It means the Scrum Team and stakeholders are open about the work and the challenges involved so important information can support effective decisions.

Question 297

Who creates the initial plan for the Sprint Backlog?

1. Developers
2. Product Owner
3. Scrum Master
4. Stakeholders

Correct Answer: 1

Explanation:

Developers create the plan contained in the Sprint Backlog. They determine how the selected work can be transformed into a usable Increment and adapt their plan throughout the Sprint as they learn more. This responsibility reflects Scrum’s self-managing approach and the Developers’ accountability for creating the Sprint plan. The Product Owner contributes information about value and Product Backlog ordering, while the Scrum Master supports effective Scrum. Neither role takes over the Developers’ responsibility for determining how the work will be accomplished. Developers also hold each other accountable as professionals for their work.

Question 298

What does Product Backlog ordering help communicate?

1. Individual Developer rankings
2. Scrum Master’s authority
3. Meeting attendance requirements
4. Relative importance of product work

Correct Answer: 4

Explanation:

Product Backlog ordering helps communicate the relative importance of the work that may contribute to improving the product. The Product Owner is accountable for ordering the Product Backlog and considers relevant information when making these decisions. Ordering can change as new evidence, customer needs, risks, dependencies, or opportunities emerge. It is therefore not necessarily permanent. Developers can provide technical information that helps inform ordering, while stakeholders can provide feedback and domain knowledge. Effective ordering helps the Scrum Team understand what work currently deserves greater attention while supporting progress toward the Product Goal.

Question 299

What does inspection require before adaptation can be effective?

1. A completely fixed Product Backlog
2. A larger Scrum Team
3. Reliable visibility into the current situation
4. A longer Sprint duration

Correct Answer: 3

Explanation:

Effective adaptation depends on having reliable information about the current situation. Transparency provides the visibility needed for meaningful inspection, while inspection examines the available information and results. If important information is hidden, misunderstood, or incomplete, the Scrum Team may make poor adaptation decisions. Scrum therefore connects the three pillars closely: transparency supports inspection, and inspection enables appropriate adaptation. A larger team or longer Sprint does not automatically improve decision-making. Similarly, the Product Backlog does not need to be permanently fixed. Scrum expects information and plans to evolve as the team learns.

Question 300

What is the primary purpose of the Sprint Retrospective?

1. To plan improvements in team effectiveness
2. To approve stakeholder contracts
3. To assign individual technical tasks
4. To maximize Product Backlog size

Correct Answer: 1

Explanation:

The Sprint Retrospective is used to plan ways to increase quality and effectiveness. The Scrum Team inspects how the Sprint went, including individuals, interactions, processes, tools, and the Definition of Done. Based on that inspection, the team identifies the most helpful changes and may begin addressing them as soon as possible. The Retrospective is therefore focused on improving the team’s way of working rather than increasing backlog size or assigning technical tasks. Continuous improvement is an important part of Scrum because the team can use what it learns to improve its practices and ability to deliver valuable, useful Increments.