What is the Product Owner responsible for during the Sprint Retrospective?
(choose the best answer)
A. Summarizing and reporting the discussions to the stakeholders that they represent in the Scrum Team.
B. The Product Owner should not take part in Sprint Retrospective.
C. Participating as a Scrum Team member.
D. Capturing requirements for the Product Backlog.
Correct Answer: C
Question 72:
The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days?
(choose the best three answers)
A. The Sprint Backlog may become inaccurate.
B. Too much work is spent updating the Scrum board before the meeting.
C. The Scrum Master loses the ability to update the Gantt chart properly.
D. The Product Owner cannot accurately report progress to the stakeholders.
E. Opportunities to inspect and adapt the Sprint Backlog are lost.
F. Impediments are raised and resolved more slowly.
Correct Answer: AEF
The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary1. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments2. If the frequency of the Daily Scrum were to be lowered to every two or three days, three key concerns would be: The Sprint Backlog may become inaccurate. The Sprint Backlog is the plan for how the Developers will achieve the Sprint Goal, and it is updated throughout the Sprint as more is learned[3][3]. The Daily Scrum is a chance for the Developers to inspect the Sprint Backlog and make adjustments based on the current situation4. If the Daily Scrum is less frequent, the Sprint Backlog may not reflect the reality of the work, and the Developers may lose track of their progress and alignment with the Sprint Goal. Opportunities to inspect and adapt the Sprint Backlog are lost. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed5. The Daily Scrum is an essential event for the Developers to apply empiricism to their work, by inspecting the Sprint Backlog and adapting it to optimize the value and quality of the Increment. If the Daily Scrum is less frequent, the Developers may miss opportunities to inspect and adapt their work, and may not be able to deliver a valuable, useful Increment every Sprint. Impediments are raised and resolved more slowly. An impediment is anything that prevents the Scrum Team from delivering a product Increment. The Daily Scrum is a forum for the Developers to identify and communicate any impediments that affect their work, and to seek help from the Scrum Master or other team members. If the Daily Scrum is less frequent, the impediments may not be raised and resolved in a timely manner, and may cause delays or quality issues in the product delivery. References:
1: The Scrum Guide, November 2020, p. 10
2: The Scrum Guide, November 2020, p. 11 [3][3]: The Scrum Guide, November 2020, p. 10
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
5: The Scrum Guide, November 2020, p. 4 The Scrum Guide, November 2020, p. 11 The Scrum Guide, November 2020, p. 14 Developing People and Teams, Scrum.org, accessed on December 16, 2023
Question 73:
The Scrum Team should have all the skills needed to:
(choose the best answer)
A. Complete the project within the date and cost as calculated by the Product Owner.
B. Do all of the development work, except for specialized testing that requires additional tools and environments.
C. Turn Product Backlog items into a valuable, useful Increment.
Correct Answer: C
Explanation: The Scrum Team should have all the skills needed to turn Product Backlog items into a valuable, useful Increment, as this is the primary goal of each Sprint. The Scrum Guide states that "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."1 The Scrum Team should be cross-functional, which means that the Developers have all the skills necessary to create a product Increment.1 The Scrum Team should also be self-managing, which means that they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1 References:
1: The Scrum Guide2, page 6
2: The Scrum Guide
Question 74:
Who is accountable for creating a valuable and usable Increment each Sprint?
(choose the best answer)
A. The Developers.
B. The CEO.
C. The Product Owner.
D. The Scrum Master.
E. The Scrum Team.
Correct Answer: A
Explanation: The Scrum Team member who is accountable for creating a valuable and usable Increment each Sprint is 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 Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery. It must be in useable condition regardless of whether it will be released or not.
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 CEO, the Product Owner, the Scrum Master, or the Scrum Team, are not accountable for creating a valuable and usable Increment each Sprint. They may have different roles and accountabilities in Scrum, but they
do not do the actual work of creating a "Done" Increment.
For the purpose of transparency, when does Scrum say a valuable and useful Increment must be available?
(choose the best answer)
A. At the end of every Sprint.
B. Every 3 Sprints.
C. Before the Release Sprint.
D. After the Acceptance Testing phase.
E. When the Product Owner asks to create one.
Correct Answer: A
The Scrum Guide states that "The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be `Done,' which
means it must be in useable condition and meet the Scrum Team's definition of `Done.'"1 This means that a valuable and useful Increment must be available at the end of every Sprint, regardless of the release frequency or the Product
Owner's request. This ensures transparency, feedback, and continuous improvement.
References:
1: The Scrum Guide2, page 14
2: The Scrum Guide
Question 76:
What is the responsibility of the Product Owner in crafting the Sprint Goal?
(choose the best answer)
A. The Product Owner has no responsibility for the Sprint Goal. It is the sole responsibility of the Developers.
B. The Product Owner cannot attend Sprint Planning without having documented the Sprint Goal in advance.
C. The Product Owner should come to Sprint Planning with a business objective in mind and work with the Developers to craft the Sprint Goal.
D. The Product Owner must work with stakeholders to set each Sprint's Goal.
E. The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal.
Correct Answer: C
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. 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 Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment. The responsibility of crafting the Sprint Goal is shared by both the Product Owner and the Developers. The Product Owner should come to Sprint Planning with a business objective in mind, based on their understanding of the product vision, goals, value proposition, stakeholder feedback, market conditions, or other relevant factors. The Product Owner should propose how this objective can be achieved by selecting some Product Backlog items that can deliver value to customers or users. The Developers should collaborate with the Product Owner to craft a clear and concise Sprint Goal that expresses what they want to accomplish as a team during this Sprint. The Developers should also ensure that they have enough capacity and skills to deliver on this Sprint Goal. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal 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 Planning: https://www.scrum.org/resources/what-is-sprint-planning
Question 77:
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?
A. 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.
B. 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.
Correct Answer: A
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
When multiple Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
(choose the best answer)
A. Yes, in order to accurately inspect what is done.
B. Yes, but only for Scrum Teams whose work has dependencies.
C. No, each Scrum Team stands alone.
D. No, that is far too hard and must be done in a hardening Sprint.
Correct Answer: A
When multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint because: It allows them to accurately inspect what is done and what is potentially releasable. By integrating their work frequently, they can ensure that the product is in a usable and valuable state at the end of each Sprint, and that it meets the Definition of Done and the Sprint Goal. It enables them to adapt to changes and feedback faster. By integrating their work frequently, they can reduce the complexity and risk of integration, and discover and resolve any issues or dependencies sooner. They can also incorporate any new insights or requirements into their Product Backlog and Sprint Planning. It fosters collaboration and alignment among the teams. By integrating their work frequently, they can share their learnings and best practices, and coordinate
their efforts towards a common vision and goal. They can also leverage the collective intelligence and creativity of the teams to deliver a better product.
References:
Scrum Guide 2020, page 10: "When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means. Although this varies significantly per Scrum Team, members must have a shared
understanding of what it means for work to be complete, to ensure transparency." Scrum Guide 2020, page 10: "The moment a Product Backlog item meets the Definition of Done, an Increment is born."
Scrum Guide 2020, page 10: "Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together." Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of
potentially releasable functionality that adhere to the Scrum Team's current Definition of Done."
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."
Question 79:
True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.
A. True
B. False
Correct Answer: A
The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. 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. An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. The Scrum Team is accountable for creating a valuable increment every Sprint, not just once or occasionally. This means that the Scrum Team must deliver a product functionality that provides value to the customers and users and contributes to the product goals and missions. The value of an increment can be measured by various factors, such as customer satisfaction, feedback, revenue, market share, or social impact. The Scrum Team is also accountable for creating a valuable increment every Sprint, not just any increment. This means that the Scrum Team must deliver a product functionality that meets the quality standards and expectations of the customers and users and complies with the Definition of Done. The quality of an increment can be measured by various factors, such as usability, reliability, performance, security, or maintainability. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team Increment: https://www.scrum.org/resources/what-is-an-increment
Question 80:
When should the Product Owner update the project plan?
(choose the best answer)
A. Before the Sprint Planning to know how much work will have to be done in the Sprint.
B. The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
C. After the Daily Scrum to ensure an accurate daily overview of project progress.
D. The project plan must be updated prior to the Sprint Retrospective.
Correct Answer: B
Explanation: Explanation: The Product Owner is responsible for managing and refining the Product Backlog, which is the single source of truth for the plan of the product development. The Product Backlog is a living artifact that changes as
the product and the market evolve. The Product Owner updates the Product Backlog continuously based on feedback, learning, and stakeholder needs. There is no separate project plan document in Scrum.
References:
[Scrum Guide], section 3.1: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."
[Professional Scrum Product Owner], chapter 5: "The Product Backlog represents everything necessary to develop and launch a successful product." [What is a Product Backlog?]: "The Product Backlog is a list of all things that need to be
Nowadays, the certification exams become more and more important and required by more and more enterprises when applying for a job. But how to prepare for the exam effectively? How to prepare for the exam in a short time with less efforts? How to get a ideal result and how to find the most reliable resources? Here on Vcedump.com, you will find all the answers. Vcedump.com provide not only Scrum exam questions, answers and explanations but also complete assistance on your exam preparation and certification application. If you are confused on your PSPO-I exam preparations and Scrum certification application, do not hesitate to visit our Vcedump.com to find your solutions here.