True or False: Scrum has a role called "Project Manager".
Correct Answer:
B
Scrum does not have the role of Project Manager. The work is completed by the three roles in the Scrum Team: Product Owner, Development Team, and Scrum Master123. Project Managers can work on any type of project, while Scrum Masters are exclusive to Scrum projects and Scrum teams2.
Which metrics will help a Product Owner determine if a product is delivering value? (choose the best two answers)
Correct Answer:
AD
The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:
✑ Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.
✑ Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.
Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.
References:
✑ Professional Scrum Product Owner™ Training, page 5, section “Product Value”
✑ Professional Scrum Product Owner™ Training, page 6, section “Product Vision”
✑ Professional Scrum Product Owner™ Training, page 7, section “Product Backlog Management”
✑ Professional Scrum Product Owner™ Training, page 8, section “Release Management”
✑ Professional Scrum Product Owner™ Training, page 9, section “Business
Strategy”
✑ Professional Scrum Product Owner™ Training, page 10, section “Stakeholders & Customers”
When is the Sprint Backlog created? (choose the best answer)
Correct Answer:
D
The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned. References:
✑ 1: The Scrum Guide2, page 15
✑ 2: The Scrum Guide
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”
Which two things should the Scrum Team do during the first Sprint? (choose the best two answers)
Correct Answer:
DE
the first Sprint is the same as any other Sprint, and the Scrum Team should deliver a potentially releasable Increment of "Done" product at its conclusion. This means that the team should build at least one piece of valuable functionality that meets the Definition of Done and aligns with the Sprint Goal. The other options are not things that the Scrum Team should do during the first Sprint, as they are either too detailed, too vague, or too long-term for the Scrum framework. The Scrum Team should not make up a plan for the rest of the project, as Scrum is an empirical process that adapts to changing requirements and feedback1. The Scrum Team should not define the major product features and a release plan architecture, as these are the responsibilities of the Product Owner, who should have a vision and a roadmap for the product2. The Scrum Team should not analyze, describe, and document the requirements for the subsequent Sprints, as this would violate the principle of emergent design and just-in-time planning3.
1: The Scrum Guide | Scrum.org 2: What is a Product Owner? | Scrum.org 3: Emergent Design and Just-in-Time Planning | Scrum.org
