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

 

Question 201

Which Scrum concept limits the risk of working too long without feedback?

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

Correct Answer: 3

Explanation:

The Sprint provides a fixed-length cycle in which the Scrum Team works toward a valuable outcome and regularly inspects what has been achieved. Because a Sprint lasts one month or less, the team does not have to wait indefinitely before receiving feedback and adapting its direction. Short, consistent cycles help limit the risk associated with uncertainty. The Product Goal provides longer-term direction, the Product Backlog represents ordered product work, and the Definition of Done establishes quality criteria. The Sprint provides the recurring structure that brings these elements together for empirical development.

Question 202

Who decides how much work can be accomplished during a Sprint?

1. Developers
2. Product Owner
3. Scrum Master
4. External stakeholders

Correct Answer: 1

Explanation:

Developers determine how much work they can realistically accomplish during a Sprint. They consider the Sprint Goal, available capacity, technical complexity, dependencies, and their understanding of the work. The Product Owner provides information about value and can help clarify Product Backlog items, but does not dictate how much work Developers must accept. The Scrum Master facilitates effective Scrum rather than assigning workload. Stakeholders can provide useful information but do not select the amount of work Developers commit to their Sprint plan. This supports self-management and realistic planning.

Question 203

What does a Sprint Goal help the Scrum Team avoid?

1. Measuring employee attendance
2. Maintaining unrelated priorities
3. Replacing the Product Goal
4. Losing sight of the Sprint’s purpose

Correct Answer: 4

Explanation:

The Sprint Goal gives the Scrum Team a clear objective for the Sprint and helps maintain focus on why the Sprint is valuable. Without a shared objective, the team could become overly focused on individual Product Backlog items without understanding the broader purpose behind the work. The Sprint Goal does not replace the Product Goal; instead, it represents a shorter-term objective that contributes toward the product’s longer-term direction. It also does not concern employee attendance. A clear Sprint Goal allows Developers to adapt detailed work while maintaining a coherent purpose.

Question 204

Which activity is not a formal Scrum event?

1. Sprint Review
2. Product Backlog Refinement
3. Sprint Retrospective
4. Sprint Planning

Correct Answer: 2

Explanation:

Product Backlog refinement is an ongoing activity rather than a formal Scrum event. During refinement, details such as descriptions, order, and size may be added or adjusted to help make upcoming work sufficiently understood. Scrum’s formal events are the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Refinement can take place throughout the Sprint as the Scrum Team learns more about the product and upcoming work. Treating refinement as an ongoing activity gives the team flexibility to prepare future Product Backlog items without creating another mandatory event with a prescribed timebox.

Question 205

What does the Sprint Backlog include besides selected work?

1. A legal contract
2. A release guarantee
3. An actionable plan
4. An employee ranking

Correct Answer: 3

Explanation:

The Sprint Backlog contains the Sprint Goal, the Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment. The plan is created and managed by Developers and evolves as they learn more. A legal contract, employee ranking, or release guarantee is not a component of the Sprint Backlog. The artifact provides transparency into the current Sprint and the Developers’ understanding of how they intend to achieve its objective. Because the plan is adaptive, it can change without undermining the Sprint Goal.

Question 206

Which Scrum value supports speaking up about difficult issues?

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

Correct Answer: 1

Explanation:

Courage is the Scrum value that supports addressing difficult issues and doing the right thing when circumstances are challenging. Scrum Teams work in complex environments where uncertainty, technical problems, disagreements, and unexpected discoveries are normal. Courage helps people raise concerns rather than hiding them simply because they are uncomfortable. Openness also supports transparency, while Focus helps direct attention toward important objectives and Respect supports professional collaboration. The values work together, but Courage is particularly relevant when team members need to confront difficult situations or challenge assumptions.

Question 207

What should happen to work that fails the Definition of Done?

1. It is automatically released
2. It is treated as completed Increment work
3. It is considered unfinished
4. It becomes the next Product Goal

Correct Answer: 3

Explanation:

Work that does not satisfy the Definition of Done is considered unfinished and cannot be treated as part of the completed Increment. This rule protects transparency by ensuring that everyone has a consistent understanding of what completed work means. The team may continue working on the item in a later Sprint, depending on its relevance and priority. It is not automatically released or transformed into a Product Goal. The Definition of Done therefore provides an important quality boundary between completed product work and work that still requires additional effort.

Question 208

Why does the Product Backlog remain ordered?

1. To identify relative priority among possible work
2. To prevent all future changes
3. To assign Developers permanently
4. To document historical meetings

Correct Answer: 1

Explanation:

The Product Backlog is ordered so that the Scrum Team and stakeholders have transparency about the relative priority of potential product work. Ordering helps the Product Owner decide which opportunities should receive attention sooner based on current understanding of value, risk, dependencies, and other relevant factors. The ordering is not permanent because the Product Backlog is emergent. It also does not assign Developers permanently or serve as a historical meeting archive. Maintaining useful ordering allows the Product Owner to guide product development while adapting to new information.

Question 209

Which Scrum artifact is directly associated with the Sprint Goal?

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

Correct Answer: 2

Explanation:

The Sprint Goal is the commitment associated with the Sprint Backlog. The Sprint Backlog contains the Sprint Goal, selected Product Backlog items, and the actionable plan for achieving the objective. The Product Backlog is associated with the Product Goal, while the Increment is associated with the Definition of Done. Understanding these relationships helps clarify the purpose of each Scrum artifact and commitment. Developers use the Sprint Backlog as their current plan and adapt it during the Sprint while maintaining focus on the Sprint Goal.

Question 210

What does the Scrum Team inspect during a Retrospective?

1. Customer invoices
2. Competitor salaries
3. Product advertising budgets
4. How the Sprint went

Correct Answer: 4

Explanation:

During the Sprint Retrospective, the Scrum Team inspects how the Sprint went, including people, interactions, processes, tools, and the Definition of Done. The purpose is to identify the most helpful changes that could improve quality and effectiveness. The Retrospective is not intended to review customer invoices, competitor salaries, or advertising budgets. The team reflects on its own way of working and determines practical improvements. These improvements may then be addressed in future work, helping the Scrum Team continuously improve rather than repeating ineffective practices from one Sprint to the next.

Question 211

Which accountability includes communicating the Product Goal?

1. Product Owner
2. Developers
3. Scrum Master
4. Stakeholder group

Correct Answer: 1

Explanation:

The Product Owner is accountable for developing and explicitly communicating the Product Goal. The Product Goal describes the future state of the product and gives the Scrum Team a longer-term objective. Developers contribute technical expertise and create the Increment, while the Scrum Master supports effective Scrum. Stakeholders can provide useful product information but do not own this accountability. Clearly communicating the Product Goal helps everyone understand the direction of the product and provides context for Product Backlog decisions and Sprint-level objectives.

Question 212

What allows Scrum Teams to make decisions using actual results?

1. Fixed assumptions
2. Empiricism
3. Annual forecasting
4. Permanent task assignments

Correct Answer: 2

Explanation:

Empiricism allows Scrum Teams to make decisions based on observation and experience. Instead of relying exclusively on predictions, the team regularly examines actual product results, progress, and changing circumstances. This approach is especially useful for complex work where future conditions cannot be fully predicted. Transparency provides a basis for inspection, and inspection supports adaptation when necessary. Fixed assumptions and permanent task assignments can become outdated when new information appears. Annual forecasting may provide context, but empirical decisions depend on learning from what actually happens during product development.

Question 213

What happens to the Sprint Backlog when new work is discovered?

1. It must remain unchanged
2. It is discarded
3. It can be updated by Developers
4. It becomes the Product Backlog

Correct Answer: 3

Explanation:

Developers can update the Sprint Backlog when new work is discovered or when their understanding of existing work changes. The Sprint Backlog is an evolving plan rather than a document that becomes frozen after Sprint Planning. Developers determine what adjustments are needed to make progress toward the Sprint Goal. New work does not cause the Sprint Backlog to become the Product Backlog, nor does discovery require discarding the existing plan. Adaptation allows Developers to respond to reality while maintaining focus on the objective established for the Sprint.

Question 214

Which statement describes Scrum’s approach to complex work?

1. Every requirement must be known before development
2. Plans should never change
3. Stakeholders should be excluded from inspection
4. Learning is used to adapt decisions

Correct Answer: 4

Explanation:

Scrum recognizes that complex work contains uncertainty and that useful knowledge emerges through experience. Therefore, Scrum encourages teams to inspect actual results and use what they learn to adapt decisions. This does not mean planning is unnecessary; planning occurs repeatedly at different levels, including Sprint Planning and ongoing Sprint Backlog adaptation. However, plans are not treated as permanent predictions. Stakeholder participation can also provide important feedback and information. Scrum’s empirical approach allows the team to respond to new evidence instead of assuming that all important details can be known before development begins.

Question 215

Who manages the Sprint Backlog?

1. Product Owner
2. Developers
3. Scrum Master
4. Executive leadership

Correct Answer: 2

Explanation:

Developers manage the Sprint Backlog because they are responsible for creating the plan needed to accomplish the Sprint Goal. They update the plan as their understanding changes and determine the most effective way to organize their work. The Product Owner is accountable for Product Backlog management, while the Scrum Master supports Scrum effectiveness. Executive leadership does not take ownership of the Developers’ Sprint plan. Giving Developers control of their plan supports self-management and ensures that the people doing the technical work can respond directly to discoveries made during implementation.

Question 216

What is the purpose of transparency in Scrum?

1. To make important information understandable
2. To eliminate every disagreement
3. To guarantee product success
4. To prevent inspection

Correct Answer: 1

Explanation:

Transparency means important aspects of the process and product are visible and understood sufficiently for meaningful inspection. Scrum depends on transparency because people cannot inspect something effectively if its relevant state is hidden or misunderstood. Transparency does not guarantee product success or eliminate every disagreement. It actually makes inspection possible, which can reveal differences in perspectives or unexpected results. Once relevant information is transparent, the Scrum Team and stakeholders can inspect the situation and determine whether adaptation is necessary. Transparency therefore forms a foundation for empirical decision-making.

Question 217

Which role helps coach the organization in Scrum?

1. Product Owner
2. Developers
3. Scrum Master
4. Customer representative

Correct Answer: 3

Explanation:

The Scrum Master helps coach the organization in Scrum and supports people in understanding and applying the framework effectively. This can include teaching Scrum principles, helping identify organizational impediments, and supporting changes that improve Scrum effectiveness. The Scrum Master does not become the manager of Developers or take over Product Owner decisions. Developers focus on creating the Increment, while the Product Owner focuses on product value and Product Backlog management. Organizational coaching helps Scrum operate beyond individual events and encourages a broader understanding of empiricism and self-management.

Question 218

What does the Product Owner use Product Backlog ordering to support?

1. Maximizing product value
2. Controlling technical implementation
3. Managing employee attendance
4. Scheduling organizational holidays

Correct Answer: 1

Explanation:

Product Backlog ordering supports the Product Owner’s accountability for maximizing product value. By considering relevant information such as value, risk, dependencies, and learning, the Product Owner can determine which work should receive attention sooner. Ordering does not give the Product Owner control over technical implementation, which remains with Developers. Employee attendance and organizational holidays are also outside the purpose of Product Backlog ordering. Because product circumstances can change, the ordering can be revised as new evidence becomes available. This keeps the backlog aligned with the product’s current needs and opportunities.

Question 219

What is the Sprint Review not intended to be?

1. A product inspection opportunity
2. A stakeholder collaboration session
3. A working session about future direction
4. A formal employee performance appraisal

Correct Answer: 4

Explanation:

The Sprint Review is not a formal employee performance appraisal. Its purpose is to inspect the Sprint outcome and collaborate with stakeholders about what to do next. Participants can discuss the Increment, relevant environmental changes, feedback, and possible Product Backlog adaptations. Individual employee evaluation belongs outside the purpose of this Scrum event. Treating the Review as an appraisal meeting would distract from its product-focused objective. The event works best when participants use actual product evidence and relevant information to understand the current state and consider useful future actions.

Question 220

What is the relationship between inspection and adaptation?

1. Inspection replaces adaptation
2. Adaptation occurs before any observation
3. Inspection can reveal when adaptation is needed
4. Neither is part of Scrum

Correct Answer: 3

Explanation:

Inspection and adaptation work together within Scrum’s empirical approach. Inspection involves examining the current state of the product, progress, or process, while adaptation involves making changes when inspection shows that an adjustment is needed. Adaptation therefore should be informed by what has been observed rather than performed randomly. Transparency makes inspection meaningful because relevant information must be visible. These principles help Scrum Teams respond to changing conditions and newly discovered information. The goal is not to change everything continuously, but to make appropriate adjustments when evidence indicates that doing so can improve outcomes.