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

 

Question 1

Who is accountable for maximizing Scrum Team value?

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

Correct Answer: 1

Explanation:

The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team’s work. This includes effective Product Backlog management, communicating the Product Goal, and ensuring that the backlog is transparent and understood. The Product Owner may delegate some responsibilities to others, but accountability remains with the Product Owner. Developers focus on creating the usable Increment, while the Scrum Master helps establish Scrum and improve effectiveness. Stakeholders provide valuable input and feedback but do not own the Product Owner’s accountability. Understanding these accountabilities is fundamental to applying Scrum correctly.

Question 2

What establishes the formal boundaries of Scrum?

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

Correct Answer: 2

Explanation:

The Scrum Guide defines Scrum and establishes the framework’s accountabilities, events, artifacts, and rules. Scrum is intentionally lightweight, so organizations may add complementary practices, but those additions should not be confused with Scrum itself. The Sprint Backlog helps Developers plan their work, the Product Goal describes a future state of the product, and the Definition of Done establishes the quality state required for an Increment. None of these defines the complete Scrum framework. Therefore, when determining what officially constitutes Scrum, the Scrum Guide is the authoritative reference.

Question 3

Which Scrum event provides an opportunity to inspect progress toward the Sprint Goal?

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

Correct Answer: 2

Explanation:

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. Although other Scrum events also involve inspection, the Daily Scrum specifically gives Developers a frequent opportunity to evaluate their progress during the Sprint. Sprint Planning focuses on establishing the Sprint Goal and selecting work. The Sprint Review is used to inspect the Sprint outcome with stakeholders, while the Sprint Retrospective focuses on improving quality and effectiveness. The Daily Scrum therefore supports short-cycle inspection and adaptation during the Sprint.

Question 4

What should happen when a Sprint Goal becomes obsolete?

1. Developers extend the Sprint duration
2. Stakeholders replace the current Sprint Backlog
3. Scrum Master creates another Sprint Goal
4. Product Owner cancels the Sprint

Correct Answer: 4

Explanation:

Only the Product Owner has the authority to cancel a Sprint, and a Sprint may be cancelled if the Sprint Goal becomes obsolete. The Sprint Goal provides the Sprint with its purpose and flexibility. If that purpose is no longer relevant, continuing the Sprint may no longer make sense. The Sprint is not extended simply because circumstances changed, and the Scrum Master does not independently replace the Sprint Goal. Developers also do not replace the Sprint’s purpose by modifying the backlog arbitrarily. The Product Owner makes the cancellation decision when the Sprint Goal has become obsolete.

Question 5

Which artifact provides transparency about upcoming product work?

1. Product Backlog
2. Sprint Backlog
3. Increment
4. Product Goal

Correct Answer: 1

Explanation:

The Product Backlog is an ordered, emergent list of everything needed to improve the product. It provides transparency into potential future work and evolves as more is learned about the product, its users, and its environment. The Sprint Backlog contains the work selected for the current Sprint rather than the broader product work. The Increment represents completed valuable work, while the Product Goal describes a future state of the product. The Product Backlog therefore gives the clearest view of upcoming product work and continuously adapts as new information becomes available.

Question 6

Who creates the Sprint Goal during Sprint Planning?

1. Scrum Master independently
2. Developers alone
3. Scrum Team collaboratively
4. Product stakeholders collectively

Correct Answer: 3

Explanation:

The Scrum Team collaboratively creates the Sprint Goal during Sprint Planning. The Product Owner helps explain why the Sprint is valuable and discusses the most important Product Backlog items. Developers consider what can realistically be accomplished and how the selected work can contribute toward the objective. The Scrum Master facilitates the event and helps ensure that Scrum is understood and applied effectively. However, the Sprint Goal is not imposed unilaterally by one person. Collaboration allows the team to establish a shared objective that provides direction throughout the Sprint.

Question 7

What is the maximum length of a Scrum Sprint?

1. Two weeks
2. One calendar month
3. Six weeks
4. One quarter

Correct Answer: 2

Explanation:

A Sprint is a fixed-length event of one month or less. Shorter Sprints can be used when they help create more frequent opportunities for inspection and adaptation. The exact duration may vary between teams, but it should remain consistent enough to establish a regular cadence. Scrum does not define a maximum of two weeks, six weeks, or one quarter. A Sprint longer than one month increases the risk that assumptions, market conditions, or requirements will change before inspection occurs. Therefore, one calendar month is the maximum Sprint duration defined by Scrum.

Question 8

Which Scrum artifact contains the Sprint Goal?

1. Product Backlog
2. Increment
3. Product Goal
4. Sprint Backlog

Correct Answer: 4

Explanation:

The Sprint Backlog contains the Sprint Goal, the selected Product Backlog items, and an actionable plan for delivering the Increment. The Sprint Goal gives Developers a clear objective for the Sprint while allowing flexibility in the exact work needed to achieve it. The Product Backlog contains the broader ordered work for the product. The Product Goal describes a longer-term objective for the product, while the Increment is the usable result of completed work. Keeping the Sprint Goal within the Sprint Backlog makes the current Sprint’s purpose transparent.

Question 9

When is a Product Backlog item considered part of an Increment?

1. When it satisfies the Definition of Done
2. When Developers begin implementing it
3. When the Product Owner discusses it
4. When it enters Sprint Planning

Correct Answer: 1

Explanation:

Work contributes to an Increment only when it meets the Definition of Done. The Definition of Done is a formal description of the state required for work to be considered complete and part of an Increment. Starting implementation does not make an item complete. Similarly, discussing an item with the Product Owner or selecting it during Sprint Planning does not mean the work has reached the required quality state. This distinction protects transparency and prevents unfinished work from being presented as a completed product result. Each Increment must satisfy the applicable Definition of Done.

Question 10

What is the primary purpose of the Sprint Review?

1. Assign individual performance ratings
2. Inspect the Sprint outcome
3. Approve Developers’ vacation schedules
4. Rewrite Scrum accountabilities

Correct Answer: 2

Explanation:

The Sprint Review is an opportunity for the Scrum Team and stakeholders to inspect the outcome of the Sprint and discuss what to do next. The Product Backlog may be adjusted based on what is learned during the event. It is not a performance appraisal meeting, an administrative scheduling session, or a mechanism for redefining Scrum accountabilities. The focus is on the product outcome, current progress toward the Product Goal, and changing circumstances that may influence future work. This collaborative inspection supports adaptation and helps ensure that product development remains aligned with emerging needs.

Question 11

Who is responsible for creating the Increment?

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

Correct Answer: 3

Explanation:

Developers are the Scrum Team members who create the usable Increment during the Sprint. They are accountable for creating a plan for the Sprint, maintaining quality by adhering to the Definition of Done, and adapting their plan as needed. The Product Owner focuses on maximizing product value and Product Backlog management. The Scrum Master helps establish Scrum and improve team effectiveness. Customers and other stakeholders can provide feedback and information, but they are not accountable for producing the Increment. The Developers’ work results in a usable product increment that meets the Definition of Done.

Question 12

Which principle requires Scrum decisions to rely on observation?

1. Empiricism
2. Specialization
3. Forecasting
4. Standardization

Correct Answer: 1

Explanation:

Empiricism is the foundation of Scrum and means that knowledge comes from experience and making decisions based on what is observed. Scrum uses transparency, inspection, and adaptation to apply empiricism. Transparency makes important aspects of the process visible. Inspection allows people to examine artifacts and progress. Adaptation enables adjustments when observations reveal unacceptable deviations or new information. Scrum does not depend primarily on detailed prediction or rigid standardization. Empirical decision-making helps teams respond to uncertainty rather than pretending that every future condition can be known in advance.

Question 13

What does the Definition of Done primarily establish?

1. Stakeholder meeting frequency
2. Product pricing rules
3. Completion quality standard
4. Developer work assignments

Correct Answer: 3

Explanation:

The Definition of Done establishes the formal quality state that an Increment must satisfy. When a Product Backlog item meets the Definition of Done, it contributes to an Increment that is usable and meets the team’s agreed quality expectations. The Definition of Done does not determine product pricing, assign individual Developers, or establish stakeholder meeting schedules. It creates transparency about what completed work means. If an item does not meet the Definition of Done, it cannot be considered part of the Increment. This shared understanding helps prevent ambiguity around completion and quality.

Question 14

Which event begins a new Sprint cycle?

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

Correct Answer: 1

Explanation:

Sprint Planning initiates the Sprint by establishing why the Sprint is valuable, what can be accomplished, and how the chosen work will be completed. The resulting Sprint Goal provides the objective for the Sprint, while Developers create an initial plan for delivering the Increment. The Sprint Review occurs near the end of the Sprint and focuses on inspecting the outcome. The Sprint Retrospective follows the Review and focuses on improving effectiveness. The Daily Scrum takes place during the Sprint. Thus, Sprint Planning is the event that starts each Sprint.

Question 15

How should Developers respond when Sprint work changes unexpectedly?

1. Wait for the next Sprint
2. Follow the original plan without adjustment
3. Adapt the plan while protecting the Sprint Goal
4. Ask stakeholders to manage the Sprint Backlog

Correct Answer: 3

Explanation:

Developers adapt their plan during the Sprint as more is learned, while keeping the Sprint Goal in mind. The Sprint Backlog is intentionally flexible and evolves as Developers gain a better understanding of the work required. Scrum does not require Developers to follow an obsolete plan simply because it was created during Sprint Planning. At the same time, changes should not undermine the Sprint Goal without appropriate consideration. Developers collaborate with the Product Owner when needed to clarify scope and negotiate adjustments. This flexibility supports empiricism while preserving the purpose of the Sprint.

Question 16

What is the recommended size of the Daily Scrum?

1. 30 minutes
2. 15 minutes
3. 45 minutes
4. 60 minutes

Correct Answer: 2

Explanation:

The Daily Scrum is a 15-minute event for Developers. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog when necessary. It is not intended to become a lengthy status-reporting meeting. Developers can use the event to coordinate their work and identify useful adaptations. If more detailed discussions are necessary, those discussions can occur separately after the Daily Scrum with the relevant participants. Keeping the event within its timebox encourages focus and provides a predictable opportunity for frequent inspection and adaptation throughout the Sprint.

Question 17

Who decides how selected work will be accomplished?

1. Product Owner
2. Scrum Master
3. Developers
4. Steering committee

Correct Answer: 3

Explanation:

Developers decide how the selected work will be accomplished. They possess the technical expertise needed to create an actionable plan and determine the appropriate approach for delivering the Increment. The Product Owner provides product direction and manages the Product Backlog, but does not dictate the technical implementation. The Scrum Master supports the Scrum Team and helps remove impediments without taking over Developers’ responsibilities. A steering committee is not a Scrum accountability. Giving Developers ownership of the implementation approach supports self-management and allows technical decisions to be made by the people performing the work.

Question 18

What is the main outcome expected from a Sprint?

1. A usable Increment
2. A finalized annual roadmap
3. A completed organizational audit
4. A permanent project schedule

Correct Answer: 1

Explanation:

The main outcome of a Sprint is a usable Increment that meets the Definition of Done. Scrum is designed to produce valuable, usable product increments frequently rather than waiting until the end of a large project. A roadmap can evolve over time, and organizational audits or permanent project schedules are not required outcomes of every Sprint. The Increment provides an inspectable result that can inform future decisions. Multiple Increments may be created within a Sprint, and the work can be delivered to users before the Sprint ends if it is valuable and meets the Definition of Done.

Question 19

What should happen if multiple Developers disagree technically?

1. Scrum Master automatically chooses the solution
2. Product Owner dictates the implementation
3. Developers resolve the disagreement collaboratively
4. Stakeholders vote on the technical approach

Correct Answer: 3

Explanation:

Developers are responsible for determining how work is accomplished, so technical disagreements should generally be resolved collaboratively within the group. Scrum promotes self-management rather than assigning technical decision-making authority to the Scrum Master, Product Owner, or external stakeholders. Developers can examine evidence, discuss trade-offs, conduct experiments, or seek relevant expertise to reach an informed decision. The goal is not to eliminate every disagreement but to enable the people doing the work to make appropriate technical choices. This approach supports accountability, ownership, and effective self-management within the Scrum Team.

Question 20

Which Scrum event focuses on improving team effectiveness?

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

Correct Answer: 4

Explanation:

The Sprint Retrospective is dedicated to planning ways to increase quality and effectiveness. During the event, the Scrum Team inspects how the previous Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done. The team identifies useful improvements and determines which changes should be addressed. Sprint Planning focuses on establishing the Sprint plan, the Sprint Review examines the product outcome with stakeholders, and the Daily Scrum supports daily inspection of progress. The Retrospective therefore provides the dedicated opportunity for the Scrum Team to improve how it works.