Practice Free PSPO-I Exam Online Questions
Question #41
A Product Backlog is: (Choose the best three answers)
- A . Ordered based on priority, value, dependencies, and risk.
- B . Only visible to the Product Owner and stakeholders.
- C . An inventory of things to be done for the Product.
- D . An exaustive list of upfront approved requirements to be implemented.
- E . Managed by the Product Owner.
Correct Answer: A,C,E
Question #42
True or False: The Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.
- A . TRUE
- B . FALSE
Correct Answer: B
Question #43
True or False: A Scrum Master fulfills the same role as a traditional Project Manager.
- A . True
- B . False
Correct Answer: B
B
Explanation:
A Scrum Master does not fulfill the same role as a traditional Project Manager. A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project 1. A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team’s progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3]. A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.
Reference:
1: What is Project Management?, Project Management Institute, accessed on December 16, 2023
2: The Scrum Guide, November 2020, p. 7
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
4: Developing People and Teams, Scrum.org, accessed on December 16, 2023
B
Explanation:
A Scrum Master does not fulfill the same role as a traditional Project Manager. A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project 1. A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team’s progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3]. A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.
Reference:
1: What is Project Management?, Project Management Institute, accessed on December 16, 2023
2: The Scrum Guide, November 2020, p. 7
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
4: Developing People and Teams, Scrum.org, accessed on December 16, 2023
Question #44
True or False: An Increment must be released to customers or users at the end of each Sprint.
- A . TRUE
- B . FALSE
Correct Answer: B
Question #45
Who is on the Scrum Team? (choose all that apply)
- A . Scrum Master.
- B . Product Owner.
- C . Developers.
- D . Project Manager.
- E . None of the above.
Correct Answer: ABC
ABC
Explanation:
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.
Reference: The Scrum Guide
The Scrum Team
Professional Scrum Product Owner™ I Certification
ABC
Explanation:
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.
Reference: The Scrum Guide
The Scrum Team
Professional Scrum Product Owner™ I Certification
Question #46
Why does the Product Owner want the Developers to adhere to its Definition of Done? (Choose the best answer)
- A . To be able to reprimand the team when they do not meet their velocity goal for the Sprint.
- B . To predict the team’s productivity over time.
- C . To have complete transparency into what has been done at the end of each Sprint.
- D . To know what the team will deliver over the next three Sprints.
Correct Answer: C
Question #47
How much of the Sprint Backlog must be defined during the Sprint Planning event? (Choose the best answer)
- A . Enough so the Developers can create their forecast of what work they can do.
- B . Just enough tasks for the Scrum Master to be confident in the Developers’ understanding of the Sprint.
- C . The entire Sprint Backlog must be identified and estimated by the end of Sprint Planning.
- D . Just enough to understand design and architectural implications.
Correct Answer: A
Question #48
Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done? (Choose the best two answers)
- A . The Product Owner should not concern themselves with meeting the Definition of Done, it is the Developer’s responsibility.
- B . To be able to punish the team when they do not meet their velocity goal for the Sprint.
- C . To forecast the team’s productivity over time.
- D . To have complete transparency into what has been done at the end of each Sprint.
- E . The Definition of Done can affect the product’s total cost of ownership.
Correct Answer: D, E
Question #49
When might a Sprint be cancelled? (choose the best answer)
- A . When the Developers determine the product plan is infeasible.
- B . When it becomes clear that not everything will be finished by the end of the Sprint.
- C . When the sales department has an important new opportunity.
- D . When the Sprint Goal becomes obsolete.
Correct Answer: D
D
Explanation:
A Sprint may be cancelled when the Sprint Goal becomes obsolete.
This is because:
The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a “Done” Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints. A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.
A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.
When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.
Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.
Reference:
[Scrum Guide], page 15, section “Sprint Goal”
[Scrum Guide], page 9, section “Sprint”
[Scrum Guide], page 16, section “Cancelling a Sprint”
D
Explanation:
A Sprint may be cancelled when the Sprint Goal becomes obsolete.
This is because:
The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a “Done” Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints. A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.
A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.
When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.
Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.
Reference:
[Scrum Guide], page 15, section “Sprint Goal”
[Scrum Guide], page 9, section “Sprint”
[Scrum Guide], page 16, section “Cancelling a Sprint”
Question #50
User documentation is part of your Definition of Done. However, there are not enough technical writers for all teams. Your Scrum Team does not have a technical writer.
What should the Scrum Team do? (choose the best answer)
- A . The Developers on the Scrum Team should write the user documentation.
- B . Wait until you have a technical writer on your Scrum Team to take care of this.
- C . Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
- D . Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
Correct Answer: A
A
Explanation:
The Scrum Guide states that “the Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint”. It also states that “the Developers can do the work of any other role on the Scrum Team, as long as accountability is met”. Therefore, the Developers on the Scrum Team should write the user documentation, as it is part of the Definition of Done and the work needed to deliver a “Done” Increment. The other options are not acceptable, as they violate the Scrum values of commitment, focus, and respect, and they create dependencies, delays, and waste.
Reference: The Scrum Guide, section 2.2. Developers
Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.3. The Product Owner and the Definition of Done
Professional Scrum Product Owner I (PSPO I) Sample Questions, question 12
A
Explanation:
The Scrum Guide states that “the Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint”. It also states that “the Developers can do the work of any other role on the Scrum Team, as long as accountability is met”. Therefore, the Developers on the Scrum Team should write the user documentation, as it is part of the Definition of Done and the work needed to deliver a “Done” Increment. The other options are not acceptable, as they violate the Scrum values of commitment, focus, and respect, and they create dependencies, delays, and waste.
Reference: The Scrum Guide, section 2.2. Developers
Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.3. The Product Owner and the Definition of Done
Professional Scrum Product Owner I (PSPO I) Sample Questions, question 12