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

 

Question 361

What is the maximum Sprint Review duration for one month?

1. 2 hours
2. 3 hours
3. 5 hours
4. 4 hours

Correct Answer: 4

Explanation:

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Shorter Sprints usually require less time. During the event, the Scrum Team and stakeholders inspect the outcome of the Sprint and collaborate about what to do next. The Sprint Review considers progress toward the Product Goal and changes in the environment that may influence future decisions. It is a working session rather than merely a presentation. The event supports inspection and adaptation of the product and its future direction based on what has actually been learned.

Question 362

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

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

Correct Answer: 1

Explanation:

Developers determine how much work they can realistically accomplish during a Sprint. During Sprint Planning, they collaborate with the Product Owner to discuss Product Backlog items and establish a Sprint Goal. Developers then create the plan for accomplishing the selected work. Their decision should consider the Sprint Goal, current understanding, capacity, technical considerations, and other relevant information. The Product Owner does not simply assign a predetermined workload, and the Scrum Master does not decide the team’s capacity. Developers remain accountable for creating and adapting their Sprint plan.

Question 363

Which Scrum value emphasizes being open about work and challenges?

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

Correct Answer: 3

Explanation:

Openness is one of the five Scrum values. Scrum Team members and stakeholders should be open about the work and the challenges involved in product development. Transparency supports this value by making important information visible, while inspection allows the team to examine what is actually happening. Openness does not mean that every decision must be made collectively by everyone involved. Instead, it supports honest communication and visibility. The other Scrum values are Commitment, Courage, Focus, and Respect, and together they guide behavior within the Scrum framework.

Question 364

What is the main purpose of the Sprint Goal?

1. To document technical architecture
2. To provide a single objective for the Sprint
3. To define the Product Goal
4. To record stakeholder feedback

Correct Answer: 2

Explanation:

The Sprint Goal is the single objective for the Sprint and is the commitment for the Sprint Backlog. It gives the Scrum Team a shared purpose while allowing flexibility in the exact work required to achieve it. As more is learned, Developers may adapt the Sprint Backlog and clarify its scope with the Product Owner without abandoning the Sprint Goal. The Sprint Goal is different from the Product Goal, which describes a future state of the product. It also differs from technical plans and stakeholder feedback, which may inform how the team achieves the objective.

Question 365

Which statement correctly describes Product Backlog refinement?

1. It is a mandatory Scrum event
2. It happens only during Sprint Planning
3. It permanently freezes backlog items
4. It is an ongoing activity

Correct Answer: 4

Explanation:

Product Backlog refinement is an ongoing activity in Scrum. During refinement, details such as description, order, and size are added to Product Backlog items. The Scrum Team collaborates to improve understanding of future work as more information becomes available. Refinement is not a formal Scrum event and therefore does not have a prescribed timebox. It can occur as needed throughout the product development process. Effective refinement helps the Scrum Team prepare useful Product Backlog items for future consideration while maintaining the emergent nature of the backlog.

Question 366

Which accountability is responsible for establishing Scrum in an organization?

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

Correct Answer: 1

Explanation:

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. This includes helping people understand Scrum theory and practice and supporting effective Scrum adoption. The Scrum Master serves the Scrum Team, Product Owner, and organization. This accountability does not mean that the Scrum Master becomes the team’s traditional manager. Developers remain responsible for creating the Increment, while the Product Owner focuses on product value and Product Backlog management. The Scrum Master helps create conditions in which Scrum can be understood and applied effectively across the organization.

Question 367

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

1. Developer workload
2. Relative importance of items
3. Scrum Master responsibilities
4. Sprint duration

Correct Answer: 2

Explanation:

Product Backlog ordering communicates the relative importance of Product Backlog items. The Product Owner is accountable for ordering the backlog and considers factors such as product value, dependencies, risks, and relevant information when making decisions. The ordering is not permanently fixed because the Product Backlog is emergent. As the Scrum Team learns more, items can be reordered or changed. Developers can provide valuable technical information that influences ordering, but the Product Owner retains the accountability for the ordering decision. Effective ordering helps guide which work should receive attention next.

Question 368

What must an Increment satisfy before it is considered complete?

1. Stakeholder approval
2. Sprint Review attendance
3. The Definition of Done
4. Product Owner preference

Correct Answer: 3

Explanation:

An Increment must satisfy the Definition of Done before it can be considered part of the Increment. The Definition of Done establishes the formal quality state required for completed product work. Developers are accountable for adhering to it. Stakeholder approval or attendance at the Sprint Review is not what determines whether work satisfies the Definition of Done. The Increment must be usable and meet the required quality measures regardless of whether it is delivered immediately. This requirement maintains transparency and prevents incomplete work from being presented as a finished product result.

Question 369

What does the Daily Scrum allow Developers to inspect?

1. Progress toward the Sprint Goal
2. The organization’s annual strategy
3. Individual employee ratings
4. Stakeholder contracts

Correct Answer: 1

Explanation:

The Daily Scrum allows Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. It is a 15-minute event intended for the Developers of the Scrum Team. The format of the discussion is not prescribed, so Developers can choose an approach that best supports their needs. The Daily Scrum is not an employee performance review or an organizational strategy meeting. Its focus remains on the current Sprint objective and the Developers’ plan for progressing toward that objective. This creates a frequent opportunity for coordination and adaptation.

Question 370

Who may delegate Product Backlog management activities while retaining accountability?

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

Correct Answer: 2

Explanation:

The Product Owner may delegate Product Backlog management activities to others while retaining accountability for the results. Product Backlog management includes developing and communicating the Product Goal, creating and clearly communicating Product Backlog items, ordering them, and ensuring transparency. Delegation does not transfer the accountability itself. The Product Owner remains accountable for effective Product Backlog management and maximizing product value. Developers and stakeholders can contribute information and collaborate on backlog matters, but they do not automatically assume the Product Owner’s accountability simply because particular activities have been delegated.

Question 371

What does a Sprint Retrospective primarily inspect?

1. Product pricing
2. Market competition
3. Team interactions and working methods
4. Stakeholder contracts

Correct Answer: 3

Explanation:

The Sprint Retrospective focuses on inspecting how the Sprint went with regard to individuals, interactions, processes, tools, and the Definition of Done. The Scrum Team identifies the most helpful changes for improving quality and effectiveness. This makes the Retrospective an important opportunity for continuous improvement. Product pricing and market competition may be relevant during product discussions, particularly the Sprint Review, but they are not the primary focus of the Retrospective. The event encourages the Scrum Team to learn from its recent experience and identify practical improvements to its way of working.

Question 372

Which Scrum pillar follows inspection when change is needed?

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

Correct Answer: 4

Explanation:

Adaptation is the third pillar of empiricism and follows inspection when the inspected results indicate that changes are necessary. Scrum relies on transparency, inspection, and adaptation to address complex work. If an aspect of the process or resulting work deviates beyond acceptable limits, the process or material should be adjusted as soon as possible. Adaptation helps prevent further problems from developing. It does not mean making arbitrary changes without evidence. Instead, the team responds to information discovered through inspection and adjusts its approach to remain aligned with its goals.

Question 373

Which Scrum value supports dedication to achieving goals?

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

Correct Answer: 1

Explanation:

Commitment is one of the five Scrum values and reflects the Scrum Team’s dedication to achieving its goals. The team commits to its goals while working collaboratively and adapting based on what it learns. Commitment does not mean blindly following an outdated plan. Scrum is empirical, so the team may change its approach when inspection reveals new information. The Sprint Goal provides the objective for the current Sprint, while the Product Goal provides longer-term product direction. Commitment works alongside Focus, Courage, Openness, and Respect to guide effective Scrum behavior.

Question 374

What does the Sprint Backlog contain besides selected Product Backlog items?

1. Release approval and stakeholder contracts
2. Sprint Goal and actionable plan
3. Product Goal and Definition of Done
4. Historical performance metrics

Correct Answer: 2

Explanation:

The Sprint Backlog contains the Sprint Goal, the selected Product Backlog items, and an actionable plan for delivering the Increment. It represents the Developers’ current plan for achieving the Sprint Goal. Because new information emerges during the Sprint, the plan can change as needed. The Product Goal belongs to the Product Backlog, while the Definition of Done is the commitment associated with the Increment. Historical performance information and stakeholder contracts are not components of the Sprint Backlog. Its purpose is to make the current Sprint work and plan transparent.

Question 375

Which Scrum event is specifically limited to 15 minutes?

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

Correct Answer: 3

Explanation:

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog when necessary. The other Scrum events have different timeboxes. Sprint Planning can take up to eight hours for a one-month Sprint, Sprint Review up to four hours, and Sprint Retrospective up to three hours. These are maximum timeboxes for one-month Sprints and are generally shorter for shorter Sprints. The Daily Scrum’s short duration supports focused daily coordination.

Question 376

What happens when a Product Backlog item does not meet the Definition of Done?

1. It automatically becomes an Increment
2. The Scrum Master approves it
3. It remains unfinished
4. Stakeholders decide whether it counts

Correct Answer: 3

Explanation:

A Product Backlog item that does not meet the Definition of Done remains unfinished and cannot be considered part of the Increment. The Definition of Done establishes the required quality state for completed work. Developers are accountable for adhering to it and ensuring that work included in the Increment satisfies the agreed standard. Stakeholder preference or Scrum Master approval does not override the Definition of Done. This rule protects transparency by preventing incomplete work from being represented as finished. Unfinished work can be reconsidered and managed through the Product Backlog in future planning.

Question 377

Which event is a working session rather than merely a demonstration?

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

Correct Answer: 1

Explanation:

The Sprint Review is a working session where the Scrum Team and stakeholders inspect the outcome of the Sprint and collaborate about what to do next. Although the Increment may be demonstrated, the event is broader than a simple demonstration. The team considers progress toward the Product Goal and relevant changes in the environment. This information can lead to adaptations in the Product Backlog. Sprint Planning focuses on establishing the Sprint plan, Daily Scrum focuses on progress toward the Sprint Goal, and Sprint Retrospective focuses on improving the team’s way of working.

Question 378

Which artifact is described as a concrete stepping stone toward the Product Goal?

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

Correct Answer: 2

Explanation:

The Increment is a concrete stepping stone toward the Product Goal. It is additive to all previous Increments and must be thoroughly verified to ensure that they work together. The Increment must meet the Definition of Done and be usable. Multiple Increments can be created during a Sprint, and they may be delivered before the Sprint ends. The Product Backlog represents ordered work needed to improve the product, while the Sprint Backlog represents the current Sprint plan. The Sprint Goal provides the objective for the current Sprint rather than being the product result itself.

Question 379

What does the Scrum Team inspect during Sprint Planning?

1. Only individual Developer performance
2. Only stakeholder satisfaction
3. The Product Backlog and current product context
4. Only previous Sprint velocity

Correct Answer: 3

Explanation:

During Sprint Planning, the Scrum Team considers the Product Backlog, the latest product information, and relevant context when planning the Sprint. The team discusses why the Sprint is valuable, what can be accomplished, and how the chosen work will be done. Planning is therefore based on current knowledge rather than a single historical measurement. Developers use their understanding of capacity and the work to create the Sprint plan. The resulting Sprint Backlog can later be adapted as more is learned. Sprint Planning establishes direction while preserving the ability to respond to change.

Question 380

Which statement best describes Scrum’s approach to complex work?

1. It requires a complete plan before development begins
2. It depends entirely on stakeholder predictions
3. It avoids inspection until the final release
4. It uses empiricism to learn and adapt

Correct Answer: 4

Explanation:

Scrum is founded on empiricism and lean thinking. For complex work, the future cannot always be predicted accurately in advance, so Scrum uses transparency, inspection, and adaptation to support learning. The Scrum Team creates useful product increments, inspects results, and adapts plans based on what is discovered. This approach does not eliminate uncertainty, but it provides a structured way to respond to it. A complete upfront plan is therefore not the basis of Scrum. Instead, Scrum enables teams to make decisions using actual experience, observation, and evolving understanding.