Scrum Teams are self-managing, meaning they internally decide who does what, when and how.
Correct Answer: B
Question 12
True or False: Dependencies could influence how the Product Owner orders Product Backlog items.
Correct Answer: A
Explanation: Dependencies are relationships between Product Backlog items that affect their order of implementation. For example, a Product Backlog item may depend on another one to be completed first, or it may have a dependency on a third-party system or resource. Dependencies could influence how the Product Owner orders Product Backlog items, as they may introduce risks, constraints, or uncertainties that affect the value delivery. The Product Owner should try to minimize dependencies and order the Product Backlog items in a way that maximizes value and minimizes waste. References: * [Professional Scrum Product Owner], chapter 6: "Dependencies are relationships between Product Backlog items that affect their order of implementation." * [Managing Dependencies on Agile Projects]: "Dependencies can have a significant impact on the delivery of value."
Question 13
What tactic should a Scrum Team use to divide a group of 100 people into multiple Scrum Teams? (choose the best answer)
Correct Answer: A
Explanation According to Scrum.org, when splitting a large group into multiple Scrum Teams, it can be beneficial to allow the people to self-organize into smaller teams12. This approach respects the principle of self-organization, which is a key aspect of Scrum12. It allows individuals to choose the team they feel they can contribute to most effectively12. However, it's important to note that this process should be facilitated and guided to ensure a balanced distribution of skills and capabilities across the teams12.
Question 14
Which are appropriate topics for discussion in a Sprint Retrospective? (choose the best three answers)
Correct Answer: A,C,D
Explanation Correct Answers: A, C, and D. Explanation: 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"
Question 15
In accordance with Scrum theory, how should a group of 100 people be divided into multiple Scrum Teams? (choose the best answer)
Correct Answer: C
In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing themselves into teams because: It respects the self-organization and empowerment of the people. The people are the ones who have the knowledge, skills, and experience to create and deliver the product. They are also the ones who will work together as Scrum Teams, collaborating and coordinating their efforts. Therefore, they should have the autonomy and authority to decide how to form their teams, based on their preferences, interests, and capabilities. It supports the alignment and coherence of the Scrum Teams. The people should have a clear and shared understanding of the product, the product vision, and the rules of the Scrum framework before forming their teams. This can help them to align their goals and missions, to ensure that they are working on the same product and towards the same vision. It can also help them to follow the same principles and practices of Scrum, to ensure that they are working effectively and consistently. It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a way that maximizes their collaboration and synergy. This can mean choosing team members that complement each other's skills and strengths, that have good rapport and trust, that can communicate and coordinate well, and that can deliver a valuable Increment each Sprint. Reference: Scrum Guide 2020, page 5: "Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint." Scrum Guide 2020, page 5: "Scrum Teams are self-managing, meaning they internally decide who does what, when, and how." Scrum Guide 2020, page 9: "Multiple Scrum Teams working together on a product use one Product Backlog." Scrum Guide 2020, page 9: "The Product Owner is one person, not a committee."
