CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSPO-I

Free PSPO-I Exam Braindumps (page: 7)

Page 7 of 43
PDF with 171 Questions

How often should customer satisfaction be measured?
(choose the best answer)

  1. Frequently.
  2. Quarterly.
  3. Daily.
  4. Annually.

Answer(s): A

Explanation:

Customer satisfaction is a measure of how well a product or service meets or exceeds the expectations and needs of the customers. It is an important indicator of the value and quality of a product or service, and it can affect the loyalty, retention, and profitability of the customers. Customer satisfaction should be measured frequently, as it can change over time depending on various factors, such as the market conditions, the customer feedback, the product updates, the competitor actions, and the customer behavior. Measuring customer satisfaction frequently can help the Product Owner and the Scrum Team to inspect and adapt their product vision, strategy, roadmap, backlog, and increments based on the customer needs and preferences. It can also help them to identify and resolve any issues or gaps that may affect the customer satisfaction and value delivery. Measuring customer satisfaction quarterly, daily, or annually is not optimal, as it may not reflect the current state of the customer satisfaction and may miss some opportunities or risks that may arise in between the measurement intervals. Quarterly measurement may be too slow to respond to the fast-changing market and customer demands. Daily measurement may be too noisy and costly to collect and analyze. Annual measurement may be too outdated and irrelevant to inform the product decisions.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Customer Satisfaction: https://www.agilealliance.org/glossary/customer-satisfaction/



A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
· Stability requirements

· Performance requirements
· Product Functionality
· Documentation
· Fixes
(choose the best answer)

  1. Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the "single source of truth" for all the work for the product.
  2. No. Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholders. Other types of requirements should be managed separately by the Developers. They are not the Product Owner's concern.

Answer(s): A

Explanation:

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time. The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog



You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select two conditions you should strive for in this scenario.
(choose the best two answers)

  1. Each Scrum Team should have a separate Product Backlog.
  2. There should be only one Product Owner.
  3. The product has one Product Backlog.
  4. There should be six Product Owners, one for each Scrum Team.
  5. There should be six Product Owners, reporting to a Chief Product Owner.

Answer(s): B,C

Explanation:

In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.

Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities. Therefore, each Scrum Team should not have a separate Product Backlog.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time. Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, there should be only one Product Owner for one product. In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Nexus: https://www.scrum.org/resources/what-is-nexus
LeSS: https://less.works/
SAFe: https://www.scaledagileframework.com/
Scrum of Scrums: https://www.agilealliance.org/glossary/scrum-of-scrums/



True or False: A Product Owner is essentially the same thing as a traditional Project Manager.

  1. True
  2. False

Answer(s): B

Explanation:

A Product Owner is not the same thing as a traditional Project Manager. A Product Owner is a role in

Scrum, a framework for developing, delivering, and sustaining complex products. A Project Manager is a role in traditional project management, a discipline for planning, executing, and controlling projects.
A Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time. A Project Manager is accountable for delivering the project within the predefined scope, time, and cost constraints. The Project Manager is responsible for defining and managing the project plan, resources, risks, issues, and dependencies. The Project Manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.
Some of the main differences between a Product Owner and a Project Manager are:


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Project Manager: https://www.pmi.org/about/learn-about-pmi/what-is-project-management



Page 7 of 43



Post your Comments and Discuss Scrum PSPO-I exam with other Community members:

Barbara commented on October 07, 2024
good content!
UNITED STATES
upvote