True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.
Correct Answer: A
* The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint. * An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. * The Scrum Team is accountable for creating a valuable increment every Sprint, not just once or occasionally. This means that the Scrum Team must deliver a product functionality that provides value to the customers and users and contributes to the product goals and missions. The value of an increment * can be measured by various factors, such as customer satisfaction, feedback, revenue, market share, or social impact. * The Scrum Team is also accountable for creating a valuable increment every Sprint, not just any increment. This means that the Scrum Team must deliver a product functionality that meets the quality standards and expectations of the customers and users and complies with the Definition of Done. The quality of an increment can be measured by various factors, such as usability, reliability, performance, security, or maintainability. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team * Increment: https://www.scrum.org/resources/what-is-an-increment
Question 177
Which are appropriate topics for discussion in a Sprint Retrospective? (choose the best three answers)
Correct Answer: A,C,D
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 178
What is the main role of a QA in Scrum?
Correct Answer: B
Question 179
Who should make sure everyone on the Scrum Team does their tasks for the Sprint? (choose the best answer)
Correct Answer: D
The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint. The Scrum Team is responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Scrum Team does not rely on any external authority, manager, or leader to assign or monitor their work. The Scrum Team collaborates and coordinates their work as one unit, without any hand-offs or silos. The Scrum Team also inspects and adapts their work based on empirical evidence and feedback. 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 Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The other options are not valid or relevant answers for who should make sure everyone on the Scrum Team does their tasks for the Sprint. They are either nonexistent or irrelevant roles in Scrum. They are: The Project Manager: There is no "Project Manager" role in Scrum. Scrum is a framework for developing, delivering, and sustaining complex products, not projects. A project is a temporary endeavor with a fixed scope, time, and cost. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project manager is a role in traditional project management, a discipline for planning, executing, and controlling projects. A project manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations. The Product Owner: The Product Owner is not responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner does not assign or monitor tasks to the Developers. The Product Owner collaborates with them to clarify and refine the Product Backlog items and their acceptance criteria. All of the above: This is not a valid answer because it includes two invalid options: The Project Manager and The Product Owner. Reference: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master
Question 180
What are typical accountabilities of a Product Owner?
