Which of the following is an example of an Increment? (choose the best answer)
A. A plan for the overall product release.
B. A mock-up of the product marketing materials.
C. A design for the product.
D. A product roll-out plan.
E. A valuable, useful set of product features.
F. All of the above.
Correct Answer: E
Explanation: An Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.1 An Increment is a concrete, tangible, and usable outcome of the work done by the Developers in a Sprint. It is not a plan, a mock-up, a design, or a roll-out plan, as these are not valuable or useful products in themselves. An Increment must meet the definition of "Done", which means it must adhere to the quality standards agreed upon by the Scrum Team and the stakeholders.1 An Increment must also be potentially releasable, which means it must be in a state that it could be delivered to the customer or user if the Product Owner decides so.1 References:
1: The Scrum Guide2, page 14
2: The Scrum Guide
Question 122:
Which of the following practices might help the Product Owner minimize waste in developing and sustaining the Product Backlog?
(choose the best two answers)
A. Avoid distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood.
B. Hand off ownership of the Product Backlog to someone else.
C. Remove items from the Product Backlog that have not been addressed in a long time.
D. Only fully describe Product Backlog items when it seems likely they will be implemented.
Correct Answer: CD
The practices that might help the Product Owner minimize waste in developing and sustaining the Product Backlog are:
Remove items from the Product Backlog that have not been addressed in a long time. This helps keep the Product Backlog relevant, concise, and focused on delivering value. Items that have not been addressed in a long time may indicate
that they are not important, feasible, or desirable anymore. They may also clutter or confuse the Product Backlog and make it harder to order and prioritize. Only fully describe Product Backlog items when it seems likely they will be
implemented. This helps avoid spending too much time or effort on items that may change or be discarded later. Items that are likely to be implemented soon should have more detail and precision than items that are further away or uncertain.
The level of detail and precision required for each item depends on its order, size, and complexity.
Other options, such as avoiding distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood or handing off ownership of the Product Backlog to someone
else, are not practices that might help minimize waste in developing and sustaining the Product Backlog. They may actually create more waste by reducing transparency, collaboration, alignment, or ownership.
A new Developer is having continuing conflicts with existing members of the Scrum Team, which is impacting the delivery of the Increment. If necessary, who is responsible for removing the Developer from the Scrum Team?
(choose the best answer)
A. The Product Owner is responsible, they control the return on investment (ROI).
B. The Scrum Team is responsible.
C. The Scrum Master is responsible, they remove impediments.
D. The hiring manager is responsible, they hired the Developer.
Correct Answer: B
The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a
valuable, useful Increment every Sprint[3][3]. If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the
Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4.
References:
1: The Scrum Guide, November 2020, p. 5
2: The Scrum Guide, November 2020, p. 6 [3][3]: The Scrum Guide, November 2020, p. 9
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
Question 124:
Which are characteristics of the Daily Scrum?
(choose the best two answers)
A. It is facilitated by the team lead.
B. Its location and time remain constant.
C. It consists of the Scrum Master asking the team for status.
D. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
E. It is held first thing in the morning.
F. It is free form and designed to promote conversation.
Correct Answer: BD
Scrum
the Daily Scrum is a 15-minute event for the Developers of the Scrum Team that is held at the same time and place every working day of the Sprint. 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 work1. The other options are not characteristics of the Daily Scrum, as it is not facilitated by the team lead, it does not consist of the Scrum Master asking the team for status, it is not held first thing in the morning, and it is not free form and designed to promote conversation234.
1: What is a Daily Scrum? | Scrum.org 2: What Is the Daily Scrum? | A Guide to the Daily Event - Scrum Alliance 3: What is Daily Scrum? | VivifyScrum 4: Daily Scrum | Definition and Overview - ProductPlan
Question 125:
True or False: Product Owners must specify complete acceptance criteria for a Product
Backlog item before the Developers can select the item in Sprint Planning.
A. True
B. False
Correct Answer: B
Answer: False Very Short Explanation: According to Scrum.org, the Product Owner is not required to create clear and unambiguous acceptance criteria for each item in the product's backlog before it can be selected in Sprint Planning1. Acceptance Criteria is optional and is not prescribed by Scrum12. It can be valuable, but it's not a must12. The Developers can inspect and adapt the Sprint Backlog in any way they see fit, in order to help meet the Sprint Goal2.
Question 126:
What happens if the Scrum Team cannot complete its work by the end of the Sprint?
(choose the best answer)
A. The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
B. The Sprint is extended and future Sprints use this new duration.
C. The Sprint is extended temporarily. Lessons are taken to ensure it does not happen again.
Correct Answer: A
If the Scrum Team cannot complete its work by the end of the Sprint, the Sprint does not get extended. Instead, the unfinished Sprint Backlog Items go back to the Product Backlog and can be addressed in the following Sprint12. This approach allows the team to get better at estimating and reduces complexity due to the consistency of the Scrum Events2. The Scrum Team continuously learns and adapts12.
Question 127:
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. The Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
B. 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.
C. Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
D. The Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
E. The Product Backlog is continually kept up to date with the most recent insights.
Correct Answer: E
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."
Question 128:
When is a Product Backlog item considered complete?
(choose the best answer)
A. When the item has gained product sponsor approval.
B. When the item passes all acceptance criteria.
C. When the item meets the Definition of Done.
D. At the end of the Sprint.
Correct Answer: C
Explanation: The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1. A Product Backlog item is considered complete when it meets the Definition
of Done, which means that it is usable and potentially releasable, and that it meets the quality standards set by the Scrum Team and the stakeholders2. The other options are not sufficient to determine the completeness of a Product Backlog
item, as they may not reflect the actual value and quality of the product.
References:
1: The Scrum Guide, November 2020, p. 13
2: The Scrum Guide, November 2020, p. 6
Question 129:
Which answer best describes the topics covered in Sprint Planning?
(choose the best answer)
A. Who is on the team and what team member roles will be.
B. How conditions have changed and how the Product Backlog should evolve.
C. What to do and who will do it.
D. What can be done, how to do it, and why to do it.
E. What went wrong in the last Sprint and what to do differently this Sprint.
Correct Answer: D
Sprint Planning is an event where the Scrum Team collaborates on the work to be performed during the Sprint1. The topics covered in Sprint Planning are:
What can be done. The Product Owner proposes how the product could increase its value and utility in the current Sprint, based on the Product Goal, the Product Backlog, and the latest market and stakeholder feedback. The Developers
assess the capacity and the technical feasibility of the work, and select the Product Backlog items that they can commit to for the Sprint. The Scrum Team crafts the Sprint Goal, which is a concise statement of the purpose and focus of the
Sprint2.
How to do it. The Developers plan how they will deliver a "Done" product Increment that meets the Sprint Goal. They create a plan for the first days of the Sprint, and decompose the selected Product Backlog items into smaller work items.
The Developers also identify any dependencies, risks, or impediments that may affect their work. The resulting plan is captured in the Sprint Backlog, which is owned and managed by the Developers[3][3]. Why to do it. The Product Owner
explains the value and the outcome of the work to be done in the Sprint, and how it aligns with the Product Goal and the stakeholder needs. The Product Owner also clarifies the acceptance criteria and the Definition of Done for the Product
Backlog items, and answers any questions from the Developers. The Scrum Team ensures that they have a common understanding of the Sprint Goal and the expected product Increment4.
References:
1: The Scrum Guide, November 2020, p. 9
2: The Scrum Guide, November 2020, p. 10 [3][3]: The Scrum Guide, November 2020, p. 10
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
Question 130:
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. Introduce these features at the next Daily Scrum.
B. Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal.
C. Add these features to the Product Backlog.
D. Have the Scrum Master add these features to the current Sprint.
Correct Answer: BC
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:
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:
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.
