Practice Free PSPO-II Exam Online Questions – Page 3

Question #21

Who is accountable for maintaining and communicating the Product Goal? (choose the best answer)

A . The Product Owner.
B . The Developers.
C . Executive Sponsors.
D . Stakeholders.
E . All of the above.

Question #22

The environment in which a product will be used changes and emerges continually.

What is the effect on the Product Backlog? (choose the best answer)

A . The requirements specification document, describing the Product Backlog items, must be updated to ensure stability.
B . The Product Backlog evolves to reflect what the product needs to be most valuable.
C . There is no effect, the Product Backlog must stay the same until the end of the project.
D . The Product Backlog is archived and a new Product Backlog is created to take its place

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

Option B is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is a living artifact that represents the current understanding of what the product needs to be most valuable for the customers and the stakeholders1. The Product Backlog is not a fixed or static document, but rather an emergent and dynamic one that adapts to the changing environment, needs, and feedback. The Product Owner is accountable for managing the Product Backlog and ensuring that it is transparent, ordered, and refined2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Backlog items based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product vision, value proposition, user stories, experiments, and evidence-based management, to define, validate, and prioritize the Product Backlog items5.

Option A is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a requirements specification document, but rather a list of hypotheses and assumptions that need to be tested and validated in the real world5. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation2. Updating the requirements specification document to ensure stability implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option C is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a project plan, but rather a product roadmap that guides the development of the product. The Product Backlog does not have a predefined end date or scope, but rather evolves and changes as the product grows and matures1. Keeping the Product Backlog the same until the end of the project implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option D is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a disposable artifact, but rather a cumulative and iterative one that builds on the previous work and learnings1. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes2. Archiving the Product Backlog and creating a new one implies a disruptive and wasteful approach that does not leverage the existing knowledge and feedback, and that does not optimize value delivery.

1: Product Backlog

2: Product Backlog Management

3: Empiricism

4: Stakeholders and Customers

5: Product Vision

: Product Value

: Evidence-Based Management

: [Agile Manifesto]

: [Product Roadmap]

: Product Owner Accountabilities

: Sprint Review

: Product Backlog Refinement

: [User Stories]

: [Value Proposition]

: [Experiments]

Question #23

Who is responsible for the Sprint Backlog?

A . The Developers.
B . The Scrum Master.
C . The Product Owner.
D . The Scrum Team.

Reveal Solution Hide Solution

Question #24

When should the Product Owner update the project plan? (choose the best answer)

A . After the Daily Scrum to ensure an accurate daily overview of project progress.
B . The project plan must be updated prior to the Sprint Retrospective.
C . The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
D . Before the Sprint Planning to know how much work will have to be done in the Sprint.

Reveal Solution Hide Solution

Correct Answer: C
C

Explanation:

In Scrum, there is no separate artifact called a project plan. The Product Backlog is the plan for the product development, and it contains all the features, requirements, enhancements, and fixes that are needed to deliver a valuable product. The Product Backlog is not a static or fixed document, but rather an emergent and dynamic one. It is constantly updated and refined by the Product Owner and the Developers as they learn more about the product, the users, the market, and the technology. The Product Backlog is updated whenever new information and insights emerge, which can happen at any time during the product development process. Therefore, option C is the best answer.

Option A is not correct because the Daily Scrum is not a status meeting, but rather a time-boxed event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. The Product Owner does not need to update the Product Backlog after the Daily Scrum, unless there is a significant change in the product vision, strategy, or value proposition that affects the Product Backlog items.

Option B is not correct because the Sprint Retrospective is not a time to update the Product Backlog, but rather a time-boxed event for the Scrum Team to inspect their way of working and identify potential improvements. The Product Owner does not need to update the Product Backlog before the Sprint Retrospective, unless there is a need to communicate a change in the Product Goal or the product roadmap that affects the Product Backlog items.

Option D is not correct because the Sprint Planning is not a time to know how much work will have to be done in the Sprint, but rather a time-boxed event for the Scrum Team to collaborate on selecting and planning the Product Backlog items that will deliver the Sprint Goal. The Product Owner does not need to update the Product Backlog before the Sprint Planning, unless there is a need to reorder or clarify the Product Backlog items that are the most valuable and relevant for the upcoming Sprint.

Reference:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

What is a Product Backlog?

Product Backlog Explained

Question #25

Which of the following statements about the Product Backlog are true? (choose the best two answers)

A . The Product Backlog is ordered by the Product Owner.
B . The Product Backlog should be visible to the Scrum Team and stakeholders.
C . All Product Backlog items must be expressed as user stories.
D . All Product Backlog items must be identified before the first Sprint begins.
E . Only the Product Owner can place items on the Product Backlog.
F . The Product Backlog represents the input of all stakeholders and eliminates any need for the Developers to speak to stakeholders.

Reveal Solution Hide Solution

Correct Answer: A, B
A, B

Explanation:

The Product Backlog is an ordered list of what is needed to improve the product, and it is the single source of work undertaken by the Scrum Team. The Product Owner is responsible for ordering the Product Backlog items by value, risk, priority, and dependencies. The Product Backlog should be transparent and accessible to the Scrum Team and the stakeholders, so that everyone can understand the scope and progress of the product development. Therefore, options A and B are true statements about the Product Backlog.

Option C is not true because the Product Backlog items can be expressed in various formats, such as user stories, use cases, scenarios, or any other way that clearly conveys the intent and value of the item. User stories are a common and useful technique, but not a mandatory one.

Option D is not true because the Product Backlog is not a fixed and complete specification of the product, but rather an emergent and dynamic artifact that evolves over time. The Product Backlog items are refined and clarified by the Product Owner and the Developers throughout the product development process, and new items can be added or removed as needed. The Product Backlog does not need to be fully defined before the first Sprint begins, but only enough to support the first Sprint Planning.

Option E is not true because the Product Owner is not the only source of ideas and requirements for the product. The Product Owner collaborates with the Developers and the stakeholders to discover, validate, and prioritize the Product Backlog items. The Product Owner may delegate the authority to add items to the Product Backlog to others, but remains accountable for the ordering and the value of the Product Backlog.

Option F is not true because the Product Backlog does not replace the communication and collaboration between the Developers and the stakeholders. The Product Backlog represents the input of all stakeholders, but it is not a substitute for direct feedback and interaction. The Developers need to engage with the stakeholders to understand their needs, expectations, and feedback, and to deliver a valuable product increment that meets the Sprint Goal and the Definition of Done.

Reference:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

[What is a Product Backlog?]

[Product Backlog Explained]

Question #26

Sharing people with unique skills across multiple teams will likely result in which of the following conditions? (choose the best answer)

A . Teams may wait more often, impeding the delivery of value.
B . Teams do not have to develop deep technical skills.
C . Costs are lower since expensive resources are shared.
D . More work gets done since people are better utilized.

Reveal Solution Hide Solution

Question #27

You started measuring product feature usage in your last release. You are surprised to learn that a sizable percentage of the features you thought were very important are never or rarely used.

Which of the following actions could you take to further evaluate this unexpected result? (choose all that apply)

A . Spend more time talking to users to identify the impact they seek.
B . Disable the features that have never been used and listen for feedback.
C . Run experiments to increase your understanding of what customers find valuable.
D . Examine whether the rarely used features solve the intended problem.

Reveal Solution Hide Solution

Question #28

Personas can help to: (choose the best answer)

A . Understand the needs of a set of users.
B . Formulate hypotheses about product value.
C . Understand market potential.
D . Discover key buying triggers.
E . All of the above.

Reveal Solution Hide Solution

1 2 3

Exams