PSPO-I Questions - Truly Beneficial For Your Scrum Exam (Updated 175 Questions)
View All PSPO-I Actual Exam Questions, Answers and Explanations for Free
NEW QUESTION # 79
What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning?
(choose the best answer)
- A. The Product Owner should select the Sprint Goal for the Scrum Team so that work can begin.
- B. Sprint Planning is canceled so refinement can be done first.
- C. The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.
- D. The Developers will find it difficult to create a Sprint forecast they are confident they can meet.
- E. Nothing in particular.
Answer: D
Explanation:
If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:
* Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
* The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
* The Product Owner is accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are most important and valuable for the product.
* If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the quality or value of the Increment.
Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.
References:
* [Scrum Guide], page 14, section "Sprint Planning"
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 6, section "Product Owner"
* [Scrum Guide], page 11, section "Product Backlog"
NEW QUESTION # 80
The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner hasthefinal say over the Definition of Done?
(choose the best answer)
- A. Yes, the Product Owner decides the Definition of Done. The Developers may be consulted.
- B. No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
Answer: B
Explanation:
Explanation
* The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment.
* The Definition of Done is defined by the Scrum Team, not by the Product Owner alone. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
* 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.
* The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
* The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
NEW QUESTION # 81
How is management that is external to the Scrum Team involved in the Daily Scrum?
(choose the best answer)
- A. The Product Owner represents their opinions.
- B. The Scrum Master speaks on their behalf.
- C. Managers are not required at the Daily Scrum.
- D. Management gives an update at the start of each Daily Scrum.
Answer: C
Explanation:
Explanation
Management that is external to the Scrum Team is not involved in the Daily Scrum because:
The Daily Scrum is an event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. It is not a status meeting or a reporting session for managers or other stakeholders.
The presence of external managers may hinder the self-organization, collaboration, and transparency of the Developers. It may also create pressure, interference, or distraction for the team.
The Scrum Master is responsible for ensuring that the Daily Scrum is held and that only the Developers participate. The Product Owner and other stakeholders may attend as observers, but only if the Developers find it useful.
References:
Scrum Guide 2020, page 12: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work." Scrum Guide 2020, page 13: "The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This creates focus and improves self-management." Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."
NEW QUESTION # 82
The Sprint is a time boxed Scrum event.
- A. True
- B. False
Answer: A
NEW QUESTION # 83
What are the two primary ways a Scrum Master helps a Scrum Team work at its highest level of productivity?
(choose the best two answers)
- A. By removing impediments that hinder the Scrum Team.
- B. By ensuring the meetings start and end at the proper time.
- C. By keeping high value features high in the Product Backlog.
- D. By facilitating Scrum Team decisions.
Answer: A,D
Explanation:
Scrum
The two primary ways a Scrum Master helps a Scrum Team work at its highest level of productivity are by facilitating Scrum Team decisions and by removing impediments that hinder the Scrum Team12.The Scrum Master is a facilitator and a coach, helping the team remove impediments and facilitating team decisions12.
This enables the team to focus on their work and maintain their productivity12.
NEW QUESTION # 84
Which is NOT a valid consideration when ordering a Product Backlog?
(choose the best answer)
- A. Importance to customers.
- B. Alignment with business strategy and goals.
- C. Risk.
- D. Tools and techniques.
- E. Dependencies on other Product Backlog items.
Answer: D
Explanation:
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.
The Product Owner is accountable for ordering the Product Backlog. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. The order of the Product Backlog items provides a clear and consistent indication of what is most important and urgent for the product. The order of the Product Backlog items also helps the Scrum Team and the stakeholders to plan and forecast effectively.
The tools and techniques used to create, manage, or refine the Product Backlog are not a valid consideration when ordering the Product Backlog. The tools and techniques are means to an end, not an end in themselves. The tools and techniques do not affect the value or quality of the product or service delivered. The tools and techniques may vary from one Product Owner to another, depending on their preferences, skills, or context. The tools and techniques may also change over time, as new technologies or practices emerge or evolve.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
NEW QUESTION # 85
During the Sprint, the Sprint Backlog can be modified as more is learned.
- A. TRUE
- B. FALSE
Answer: A
NEW QUESTION # 86
Why does the Product Owner want the Developers to adhere to its Definition of Done?
(choose the best answer)
- A. To predict the team's productivity over time.
- B. To know what the team will deliver over the next three Sprints.
- C. To have complete transparency into what has been done at the end of each Sprint.
- D. To be able to reprimand the team when they do not meet their velocity goal for the Sprint.
Answer: C
Explanation:
The Product Owner wants the Developers to adhere to its Definition of Done to have complete transparency into what has been done at the end of each Sprint. This is because:
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what "Done" means for any Product Backlog item that is selected for a Sprint.
The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
Having a clear and consistent Definition of Done helps the Product Owner have complete transparency into what has been done at the end of each Sprint. It also helps them make informed decisions about releasing, adapting, or continuing the product development.
Other options, such as predicting the team's productivity over time, knowing what the team will deliver over the next three Sprints, or reprimanding the team when they do not meet their velocity goal for the Sprint, are not valid reasons for wanting the Developers to adhere to its Definition of Done. They may reflect a misunderstanding of what a Definition of Done is or how Scrum works.
Reference:
[Scrum Guide], page 10, section "Definition of Done"
[Scrum Guide], page 7, section "Developers"
[Scrum Guide], page 6, section "Product Owner"
NEW QUESTION # 87
In the Daily Scrum, the Scrum Master is not allowed to attend.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 88
Which statement best describes a Product Owner's responsibility?
(choose the best answer)
- A. Directing the Developers.
- B. Ensuring that the work meets the commitments to the stakeholders.
- C. Keep stakeholders from distracting the Developers.
- D. Maximizing the value of the work the Scrum Team does.
Answer: D
Explanation:
Explanation
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 creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Product Owner does not manage the Developers, but collaborates with them and the Scrum Master to optimize the value delivery. The Product Owner does not ensure that the work meets the commitments to the stakeholders, but rather that the work delivers value to the stakeholders. The Product Owner does not keep stakeholders from distracting the Developers, but rather engages them and manages their expectations.
References:
* Professional Scrum Product Owner™ I Certification
* [The Scrum Guide]
* [The Product Owner]
NEW QUESTION # 89
What are two effective ways for the Scrum Team to make non-functional requirements visible?
(choose the best two answers)
- A. Put them on a separate list on the Scrum board, available for all to see.
- B. Add them to the Definition of Done so the work is taken care of every Sprint.
- C. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
- D. Add them to the Product Backlog to ensure transparency.
Answer: B,D
Explanation:
Explanation
Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.
References:
1: Non-functional requirement, Wikipedia, accessed on December 16, 2023
2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
[3][3]: The Scrum Guide, November 2020, p. 6
4: The Scrum Guide, November 2020, p. 7
5: The Scrum Guide, November 2020, p. 13
Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 90
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?
(choose the best answer)
- A. Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
- B. The Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
- C. The Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
- D. The Product Backlog is continually kept up to date with the most recent insights.
- E. Product Backlog items should hold no more than 8 points of work, which is the average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.
Answer: D
Explanation:
Explanation
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
* It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that
* constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
* It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
* It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.
References:
* Scrum Guide 2020, page 10: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."
* Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ensuring that the Product Backlog is transparent, visible and understood."
* Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions."
* Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones."
* Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."
NEW QUESTION # 91
Which are appropriate topics for discussion in a Sprint Retrospective?
(choose the best three answers)
- A. Arranging the Sprint Backlog for the next Sprint.
- B. The value of work currently represented in the Product Backlog.
- C. How the Scrum Team does its work.
- D. Team relations.
- E. Definition of Done.
Answer: C,D,E
Explanation:
Correct Answers: A, C, and D.
The Sprint Retrospective is an event where the Scrum Team reflects on how they worked together in the last Sprint and identifies ways to improve their collaboration, processes, and quality. Therefore, appropriate topics for discussion in a Sprint Retrospective are:
* Team relations: The Scrum Team should discuss how they communicated, interacted, and supported each other during the Sprint. They should celebrate their successes, acknowledge their challenges, and address any conflicts or issues that arose. They should also share feedback, appreciation, and suggestions for improvement with each other.
* How the Scrum Team does its work: The Scrum Team should inspect the methods, tools, and practices they used to deliver the product increment. They should evaluate what worked well and what could be improved. They should also identify any impediments, risks, or dependencies that affected their work and how they handled them.
* Definition of Done: The Scrum Team should review their Definition of Done and check if it is still relevant, clear, and achievable. They should also assess how well they adhered to it and if they delivered a potentially releasable product increment that meets the quality standards. They should also consider if they need to update or adapt their Definition of Done based on new insights or feedback.
The following topics are not appropriate for discussion in a Sprint Retrospective:
* The value of work currently represented in the Product Backlog: The value of the Product Backlog items is the responsibility of the Product Owner, who should continuously refine and order them based on stakeholder needs and feedback. The value of the Product Backlog items is not directly related to how the Scrum Team works together and does not affect their improvement actions for the next Sprint.
* Arranging the Sprint Backlog for the next Sprint: The Sprint Backlog is the plan for the next Sprint that is created by the Scrum Team during the Sprint Planning event. The Sprint Backlog is based on the Product Backlog items that are selected for the next Sprint and how the Developers intend to accomplish them. The Sprint Retrospective is not a planning event but a reflection event that focuses on the past Sprint.
[Scrum Guide], section 3.5: "The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness."
[Professional Scrum Product Owner], chapter 7: "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." What is a Sprint Retrospective? | Scrum.org: "During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done" if appropriate and not in conflict with product or organizational standards." The Sprint Retrospective - What It Is and Tips for Making the Most of Your Meeting: "The focus is on how the team worked together in the last sprint, including: Communication Teamwork Process Tools Systems Work environment Missing competencies Collaboration with external parties"
NEW QUESTION # 92
Which of the following are criteria to order Product Backlog items?
(choose all that apply)
- A. The availability of the Scrum Master.
- B. Dependencies between Product Backlog items.
- C. Value of Product Backlog items.
- D. Dependencies to other products.
- E. All of the above.
Answer: B,C,D
Explanation:
Explanation
The Product Owner orders the Product Backlog items according to various criteria, such as:
* The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users, considering factors such as customer satisfaction, market share, revenue, social impact, etc.
* The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible.
* The dependencies to other products. The Product Owner also considers the dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.
References:
* Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood."
* Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions."
* Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones."
NEW QUESTION # 93
In the middle of the Sprint, the customer decides that there are two new features she wants.
The Product Owner could:
(choose the best two answers)
- A. Add these features to the Product Backlog.
- B. Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal.
- C. Have the Scrum Master add these features to the current Sprint.
- D. Introduce these features at the next Daily Scrum.
Answer: A,B
Explanation:
* 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.
* A Sprint is a timebox of one month or less within which a "Done" product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.
* The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
* In the middle of a Sprint, if a customer decides that there are two new features she wants, there are two possible ways that a Product Owner could handle this situation:
* Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal: The Product Owner could discuss with the Developers if they have enough capacity and skills to accommodate these new features in their current Sprint Backlog.
The Product Owner could also explain why these features are valuable or urgent for the customer or user. The Developers could then decide if they can or want to add these features to their current work plan, or if they prefer to defer them to a future Sprint. The Developers should not compromise on quality or scope to fit these features in their current Sprint. The Developers should also ensure that these features are aligned with or support the current Sprint Goal.
* Add these features to the Product Backlog: The Product Owner could add these new features to the Product Backlog as new items. The Product Owner could then order these items based on their value, risk, priority, dependency, feedback, or market conditions. The Product Owner could also refine these items with more details or acceptance criteria. The Product Owner could then plan to include these items in a future Sprint, depending on their order and availability.
* The other options are not valid or relevant ways that a Product Owner could handle this situation. They are either too disruptive, impractical, or irrelevant. They are:
* Introduce these features at the next Daily Scrum: This is not a valid way for a Product Owner to handle this situation. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers. However, introducing new features at this event would be disruptive and inappropriate for both parties.
* Have the Scrum Master add these features to the current Sprint: This is not a valid way for a Product Owner to handle this situation. The Scrum Master is not responsible for adding or removing any work from the current Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
* Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum
* Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal
* Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum
* Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
NEW QUESTION # 94
Who does the work to make sure Product Backlog items conform to the Definition of Done?
(choose the best answer)
- A. The Quality Assurance Team.
- B. The Scrum Master.
- C. The Scrum Team.
- D. The Product Owner.
- E. The Developers.
Answer: E
Explanation:
Explanation
The work to make sure Product Backlog items conform to the Definition of Done is done by the Developers.
This is because:
* The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
* The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what "Done" means for any Product Backlog item that is selected for a Sprint.
* The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
Other options, such as the Product Owner, the Quality Assurance Team, the Scrum Team, or the Scrum Master, are not responsible for making sure Product Backlog items conform to the Definition of Done. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a
"Done" Increment.
References:
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 10, section "Definition of Done"
* [Scrum Guide], page 7, section "The Scrum Team"
NEW QUESTION # 95
The Scrum Master observes the Product Owner struggling with ordering the Product Backlog.
What is an appropriate action for the Scrum Master to take?
(choose the best answer)
- A. Suggest that the Developers order the Product Backlog to be sure that it is a feasibleordering of work.
- B. Encourage the Product Owner to work with the Developers to see which itemstechnically are fastest to implement.
- C. Present the Product Owner with an ordered Product Backlog to use.
- D. Suggest the Product Owner extend the Sprint, so he can have more time to order theProduct Backlog.
- E. Offer the Product Owner help in understanding that the goal of ordering the ProductBacklog is to maximize value.
Answer: E
Explanation:
The Scrum Master's role includes coaching the Scrum Team and helping them understand Scrum practices. If the Product Owner is struggling with ordering the Product Backlog, the Scrum Master should offer guidance and support to help the Product Owner understand that the primary goal of ordering the Product Backlog is to maximize the value delivered to the customer. This involves considering factors such as business value, risk, return on investment (ROI), dependencies, and impact. The Scrum Master can facilitate this understanding and help the Product Owner apply it to the ordering of the Product Backlog items.
The Scrum Guide and resources from Scrum.org provide insights into the role of the Scrum Master in supporting the Product Owner and ensuring that the Product Backlog is ordered in a way that maximizes value
NEW QUESTION # 96
The Sprint Goal is created during the Sprint Review and then added to the Sprint Backlog.
- A. FALSE
- B. TRUE
Answer: A
NEW QUESTION # 97
True or False: A Scrum Master fulfills the same role as a traditional Project Manager.
- A. True
- B. False
Answer: 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 project1. 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.
References:
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
NEW QUESTION # 98
True or False: The Product Owner must write all of the Product Backlog items (e.g., user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.
- A. True
- B. False
Answer: B
Explanation:
It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because:
* The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.
* The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
* The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.
* The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.
References:
* [Scrum Guide], page 6, section "Product Owner"
* [Scrum Guide], page 11, section "Product Backlog"
* [Scrum Guide], page 10, section "Product Goal"
* [Scrum Guide], page 12, section "Product Backlog Refinement"
* [Scrum Guide], page 14, section "Sprint Planning"
NEW QUESTION # 99
True or False: A Product Owner should measure product value by the increase in the team's velocity.
- A. True
- B. False
Answer: B
Explanation:
A Product Owner should not measure product value by the increase in the team's velocity. This is because:
* Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done.
* Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good.
* Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals.
* A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data,
* market share, return on investment, or social impact.
References:
* [Scrum Guide], page 7, section "Developers"
* [Scrum Guide], page 10, section "Definition of Done"
* [Scrum Guide], page 15, section "Sprint Backlog"
* [Professional Scrum Product Owner™ Training], page 5, section "Product Value"
* [Professional Scrum Product Owner™ Training], page 9, section "Business Strategy"
NEW QUESTION # 100
When does a new Sprint start?
- A. Immediately after the conclusion of the previous Sprint.
- B. When the Scrum Master starts it.
- C. When the Product Owner starts it.
Answer: A
NEW QUESTION # 101
Who determines how many Product Backlog items the Developers select for a Sprint?
(choose the best answer)
- A. The Scrum Team
- B. The Scrum Master.
- C. The Product Owner.
- D. The stakeholders attending Sprint Planning.
- E. The Developers.
Answer: E
Explanation:
Explanation
The Developers are the ones who determine how many Product Backlog items they select for a Sprint. The Developers are self-managing and decide how much work they can do in a Sprint1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product Backlog items they should select, as this would violate the principle of self-management[3][3].
References:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
NEW QUESTION # 102
What may be included in the Sprint Backlog?
(choose the best answer)
- A. User Stories.
- B. Tests.
- C. Tasks.
- D. Any of the above (or others) which are a decomposition of the selected Product Backlog items.
- E. Use Cases.
Answer: D
Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a
"Done" Increment1. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal1. The Sprint Backlog can include any items that the Developers deem necessary to achieve the Sprint Goal, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum1.
References:
* The Scrum Guide, section 3.3. Sprint Backlog
* Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint
* Professional Scrum Product Owner I (PSPO I) Sample Questions, question 11
NEW QUESTION # 103
......
PSPO-I dumps Free Test Engine Verified By It Certified Experts: https://www.testkingfree.com/Scrum/PSPO-I-practice-exam-dumps.html
PSPO-I Exam Free Practice Test with100% Accurate Answers: https://drive.google.com/open?id=1N4lEbfT-BGRxWjkEKMEPtV94oA8H0Z3X