Exam Dumps VCE

* 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, a Product Owner with multiple teams working on one product should not maintain separate Product Backlogs for each team.
* 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.
* 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.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Nexus: [1]
* LeSS: [2]
* SAFe: [3]
* Scrum of Scrums: [4]

Explanation
* 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

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 created by the Scrum Team, not just the Developers. The Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency. The Definition of Done is used to assess when work is complete on the product Increment. The Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and is updated whenever the Scrum Team learns more about the product and the environment in which it operates.
References:
* The Scrum Guide
* Understanding and Applying the Scrum Framework
* Professional Scrum Product Owner™ I Certification

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.”

Explanation
The Product Owner should care that the Scrum Team adheres to its Definition of Done because:
* It helps to forecast the team’s productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly.
* It affects the product’s total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs in the future.
References:
* Scrum Guide 2020, page 10: “The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”
* 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 14: “The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review.
Instead, it returns to the Product Backlog for future consideration.”

Explanation
The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
According to the Scrum Guide1, “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.” This implies that the team does not depend on external resources or specialists to deliver a product increment. The other options do not reflect the true meaning of cross-functionality in Scrum.
1: The Scrum Team | Scrum.org

Explanation
A Sprint may be cancelled when the Sprint Goal becomes obsolete. This is because:
* The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
* The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a “Done” Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints.
* A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.
* A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.
* When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.
Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.
References:
* [Scrum Guide], page 15, section “Sprint Goal”
* [Scrum Guide], page 9, section “Sprint”
* [Scrum Guide], page 16, section “Cancelling a Sprint”

The Scrum Guide states that “By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself.”1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:
* 1: The Scrum Guide2, page 16
* 2: The Scrum Guide

Explanation
During the Sprint Review, the stakeholder’s role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
* 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. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc.
* The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
* The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.
References:
* Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner.”
* 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 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.”

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.
References:
* [Scrum Guide], page 11, section “Product Backlog”
* [Scrum Guide], page 6, section “Product Owner”
* [Scrum Guide], page 12, section “Product Backlog Refinement”

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