How is management that is external to the Scrum Team involved in the Daily Scrum? (choose the best answer)
Correct Answer:
C
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.”
True or False: The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal.
Correct Answer:
A
It is true that the Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. 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 Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them as a “Done” Increment. The Sprint Backlog is owned by the Developers who use it to organize and manage their work during the Sprint.
✑ 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 Backlog is created by the collaborative work of the entire Scrum Team during Sprint Planning. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The Developers discuss how they can deliver a “Done” Increment that meets this proposal. Together, they define a Sprint Goal that summarizes why the Sprint is valuable to stakeholders. Then, they select enough Product Backlog items from the top of the ordered Product Backlog to satisfy the Sprint Goal. Finally, they create a plan for how they will deliver those items as a “Done” Increment.
References:
✑ [Scrum Guide], page 14, section “Sprint Planning”
✑ [Scrum Guide], page 15, section “Sprint Backlog”
✑ [Scrum Guide], page 15, section “Sprint Goal”
Which are appropriate topics for discussion in a Sprint Retrospective? (choose the best three answers)
Correct Answer:
ACD
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.
References:
✑ [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 & 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”
How often should customer satisfaction be measured? (choose the best answer)
Correct Answer:
A
✑ Customer satisfaction is a measure of how well a product or service meets or exceeds the expectations and needs of the customers. It is an important indicator of the value and quality of a product or service, and it can affect the loyalty, retention, and profitability of the customers.
✑ Customer satisfaction should be measured frequently, as it can change over time depending on various factors, such as the market conditions, the customer feedback, the product updates, the competitor actions, and the customer behavior. Measuring customer satisfaction frequently can help the Product Owner and the Scrum Team to inspect and adapt their product vision, strategy, roadmap, backlog, and increments based on the customer needs and preferences. It can also help them to identify and resolve any issues or gaps that may affect the customer satisfaction and value delivery.
✑ Measuring customer satisfaction quarterly, daily, or annually is not optimal, as it may not reflect the current state of the customer satisfaction and may miss some opportunities or risks that may arise in between the measurement intervals. Quarterly measurement may be too slow to respond to the fast-changing market and customer demands. Daily measurement may be too noisy and costly to collect and analyze. Annual measurement may be too outdated and irrelevant to inform the product decisions.
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Customer Satisfaction: https://www.agilealliance.org/glossary/customer- satisfaction/
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
(choose the best answer)
Correct Answer:
D
According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team’s progress.
Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.
References:
✑ [Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
✑ Accountabilities in Scrum | Scrum.org: “Scrum has three accountabilities, each with a different focus : Product Owner (green figure) The "What". With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building something that is Done – that the increment is useable and potentially releasable.”
✑ What is a Developer in Scrum? | Scrum.org: “The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. However, the Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal”
