Practice Free PSM I Exam Online Questions
Question #21
Which Scrum Value is affected by a lack of trust in the Scrum Team?
- A . Focus
- B . Respect
- C . Openness
- D . Courage
- E . Commitment.
- F . All of the above
Correct Answer: F
F
Explanation:
The correct answer is F, because all of the Scrum Values are affected by a lack of trust in the Scrum Team. Trust is essential for the Scrum Team to work effectively and deliver value. Without trust, the Scrum Team may lose focus, respect, openness, courage, and commitment.
F
Explanation:
The correct answer is F, because all of the Scrum Values are affected by a lack of trust in the Scrum Team. Trust is essential for the Scrum Team to work effectively and deliver value. Without trust, the Scrum Team may lose focus, respect, openness, courage, and commitment.
Question #22
(What are two ways that regulatory compliance requirements are dealt with in Scrum?
Choose the best two answers.)
- A . They are addressed by a separate team who is responsible for compliance issues.
- B . They are discussed, analyzed, and documented before the first Sprint can begin.
- C . They are added to the Product Backlog and addressed during each Sprint, alongside the creation of new Product capabilities.
- D . They are addressed as part of meeting the Definition of Done during each Sprint.
Correct Answer: C, D
C, D
Explanation:
In Scrum, regulatory and compliance requirements are not treated as work outside the Scrum Team or postponed until a separate phase. They must be made visible and managed as part of normal product development.
Option C is correct because any work that is needed for the product, including compliance-related requirements, should be represented in the Product Backlog. The Product Backlog is the single source of work undertaken by the Scrum Team, so compliance items are handled alongside functional and technical work during Sprints.
Option D is also correct because compliance often affects whether an Increment is truly complete. Scrum requires each Increment to meet the Definition of Done, which creates transparency about quality and completeness. If regulatory conditions are necessary for releasability or completeness, they should be included in the Definition of Done and verified every Sprint.
Options A and B are incorrect because Scrum does not promote handing compliance to a separate team or completing all compliance analysis before Sprinting starts. Scrum uses an iterative, incremental approach where such requirements are addressed continuously.
C, D
Explanation:
In Scrum, regulatory and compliance requirements are not treated as work outside the Scrum Team or postponed until a separate phase. They must be made visible and managed as part of normal product development.
Option C is correct because any work that is needed for the product, including compliance-related requirements, should be represented in the Product Backlog. The Product Backlog is the single source of work undertaken by the Scrum Team, so compliance items are handled alongside functional and technical work during Sprints.
Option D is also correct because compliance often affects whether an Increment is truly complete. Scrum requires each Increment to meet the Definition of Done, which creates transparency about quality and completeness. If regulatory conditions are necessary for releasability or completeness, they should be included in the Definition of Done and verified every Sprint.
Options A and B are incorrect because Scrum does not promote handing compliance to a separate team or completing all compliance analysis before Sprinting starts. Scrum uses an iterative, incremental approach where such requirements are addressed continuously.
Question #23
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the quality of the product, and the Product Owner agrees with the stakeholder’s assessment that the quality is low.
How should the Scrum Master respond to the Product Owner? (choose the best two answers)
- A . Encourage the Product Owner to include quality specifications in the Product Backlog and to communicate the stakeholders’ concerns to the Developers.
- B . Bring the concern to the testers to improve how the Product is verified.
- C . Work with the Product Owner to understand their desired resolution and help formulate an approach for raising the concern with the Developers.
- D . Tell the Product Owner they have noted the concern and will raise this issue at the Sprint Retrospective.
- E . Explain to the Product Owner that it is up to the Developers to decide on acceptable quality standards.
Correct Answer: AC
AC
Explanation:
Several Sprints into a project, a key stakeholder begins using the product and finds the quality lacking. The Product Owner (PO) agrees and shares this concern with the Scrum Master (SM). The Scrum Master needs to determine the best way to respond.
Scrum emphasizes empiricism, which is based on transparency, inspection, and adaptation. This means that if quality concerns arise, the Scrum Team must inspect the issue, adapt accordingly, and ensure quality is built into the product incrementally.
✅
AC
Explanation:
Several Sprints into a project, a key stakeholder begins using the product and finds the quality lacking. The Product Owner (PO) agrees and shares this concern with the Scrum Master (SM). The Scrum Master needs to determine the best way to respond.
Scrum emphasizes empiricism, which is based on transparency, inspection, and adaptation. This means that if quality concerns arise, the Scrum Team must inspect the issue, adapt accordingly, and ensure quality is built into the product incrementally.
✅
Question #24
Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose all that apply.)
- A . Definition of “Done”.
- B . How the team does its work.
- C . Team relations.
- D . The value of work currently represented in the Product Backlog.
- E . Arranging the Sprint Backlog for the next Sprint.
Correct Answer: DE
DE
Explanation:
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as processes, tools, communication, collaboration, quality, etc. The value of work currently represented in the Product Backlog and arranging the Sprint Backlog for the next Sprint are not appropriate topics for discussion in a Sprint Retrospective, as they belong to the Sprint Review and Sprint Planning events respectively.
DE
Explanation:
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as processes, tools, communication, collaboration, quality, etc. The value of work currently represented in the Product Backlog and arranging the Sprint Backlog for the next Sprint are not appropriate topics for discussion in a Sprint Retrospective, as they belong to the Sprint Review and Sprint Planning events respectively.
Question #25
Who determines how many Product Backlog items the Developers select tor a sprint? (choose the best answer)
- A . The Scrum Master
- B . The Scrum Team
- C . The Developers
- D . The stakeholders attending Sprint Planning
- E . The Product Owner
Correct Answer: C
C
Explanation:
The Developers determine how many Product Backlog items they select for a Sprint, as stated in the Scrum Guide: “The Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.”
C
Explanation:
The Developers determine how many Product Backlog items they select for a Sprint, as stated in the Scrum Guide: “The Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.”
Question #26
How much time is required after a Sprint to prepare for the next Sprint?
- A . The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.
- B . Enough time for the requirements for the next Sprint to be determined and documented.
- C . Enough time for the Development team to finish the testing from the last Sprint.
- D . None. A new Sprint starts immediately following the end of the previous Sprint.
- E . All of the above are allowed depending on the situation.
Correct Answer: D
D
Explanation:
The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that “a new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, there is no time required after a Sprint to prepare for the next Sprint.
D
Explanation:
The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that “a new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, there is no time required after a Sprint to prepare for the next Sprint.
Question #27
The Sprint Review is mainly an inspect and adapt opportunity for which group?
- A . The Development Team and stakeholders.
- B . The Product Owner and Development Team.
- C . The Scrum Team and stakeholders.
- D . The Product Owner and management.
- E . The Development Team and management.
- F . The Product Owner and stakeholders.
Correct Answer: C
C
Explanation:
According to the Scrum Guide1, the Sprint Review is an informal meeting at the end of the Sprint, where the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; the Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; and the Development Team demonstrates the work that it has “Done” and answers questions about the Increment. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is mainly an inspect and adapt opportunity for the Scrum Team and stakeholders.
Reference: Scrum Guide
C
Explanation:
According to the Scrum Guide1, the Sprint Review is an informal meeting at the end of the Sprint, where the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; the Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; and the Development Team demonstrates the work that it has “Done” and answers questions about the Increment. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is mainly an inspect and adapt opportunity for the Scrum Team and stakeholders.
Reference: Scrum Guide
Question #28
How often should Scrum Team membership change?
- A . As needed, while taking into account a short term reduction in productivity.
- B . Never, because it reduces productivity.
- C . As needed, with no special allowance for changes in productivity.
- D . Every Sprint to promote shared learning.
Correct Answer: A
A
Explanation:
The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that “development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; development Teams are self-organizing. No one (not even the Scrum Master)
tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, changing Development Team membership may affect their cross-functionality and self-organization in the short term.
A
Explanation:
The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that “development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; development Teams are self-organizing. No one (not even the Scrum Master)
tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, changing Development Team membership may affect their cross-functionality and self-organization in the short term.
Question #29
Which statement best describes a Product Owner’s responsibility?
- A . Optimizing the value of the work the Development Team does.
- B . Managing the project and ensuring that the work meets the commitments to the stakeholders.
- C . Directing the Development Team.
- D . Keep stakeholders from distracting the Development Team.
Correct Answer: A
A
Explanation:
According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the
work the Development Team does.
Reference: Scrum Guide
A
Explanation:
According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the
work the Development Team does.
Reference: Scrum Guide
Question #30
(When does a Developer become accountable for an item in the Sprint Backlog? Choose the best answer.)
- A . During the Daily Scrum.
- B . Never. All Developers on the Scrum Team share accountability for items in the Sprint Backlog.
- C . As soon as a Developer on the Scrum Team can accommodate more work.
- D . At Sprint Planning when all of the Sprint Backlog items are split evenly across the Developers.
Correct Answer: B
B
Explanation:
The correct answer is B because in Scrum, Developers are collectively accountable for creating a usable Increment every Sprint, and they share accountability for the Sprint Backlog. Scrum emphasizes self-management and collective ownership rather than assigning individual accountability for separate backlog items in the traditional sense. The Developers decide how to turn selected Product Backlog items into an Increment and how to organize their work, but the responsibility remains shared across the team.
This shared accountability supports collaboration, flexibility, and focus on the Sprint Goal. It prevents siloed behavior where individuals protect only their own tasks instead of working together to achieve the Sprint outcome. The Sprint Backlog is created by and for the Developers, and they adapt it throughout the Sprint as more is learned.
Option A is incorrect because accountability does not begin during the Daily Scrum.
Option C is incorrect because capacity does not create individual ownership in Scrum.
Option D is incorrect because Scrum does not require even task splitting or pre-assigned ownership at Sprint Planning. The Developers remain collectively accountable throughout the Sprint.
B
Explanation:
The correct answer is B because in Scrum, Developers are collectively accountable for creating a usable Increment every Sprint, and they share accountability for the Sprint Backlog. Scrum emphasizes self-management and collective ownership rather than assigning individual accountability for separate backlog items in the traditional sense. The Developers decide how to turn selected Product Backlog items into an Increment and how to organize their work, but the responsibility remains shared across the team.
This shared accountability supports collaboration, flexibility, and focus on the Sprint Goal. It prevents siloed behavior where individuals protect only their own tasks instead of working together to achieve the Sprint outcome. The Sprint Backlog is created by and for the Developers, and they adapt it throughout the Sprint as more is learned.
Option A is incorrect because accountability does not begin during the Daily Scrum.
Option C is incorrect because capacity does not create individual ownership in Scrum.
Option D is incorrect because Scrum does not require even task splitting or pre-assigned ownership at Sprint Planning. The Developers remain collectively accountable throughout the Sprint.