True or False: Cross-functional teams are optimized to work on one component or layer of a system only.
Correct Answer: B
Explanation Cross-functional teams are not optimized to work on one component or layer of a system only. This is because: * Cross-functional teams are teams that have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team. * Cross-functional teams are able to deliver value across the entire product, rather than focusing on a specific component or layer. They can work on any aspect of the product that is needed to achieve the Sprint Goal and the Product Goal. * Cross-functional teams are more agile, collaborative, and creative than teams that are specialized or siloed. They can reduce dependencies, handoffs, and delays, and increase feedback, learning, and adaptation. References: * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 10, section "Product Goal" * [Scrum Guide], page 7, section "The Scrum Team"
Question 122
True or False: The Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.
Correct Answer: B
It is not true that the Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This is because: * The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness. * The Sprint Retrospective is an internal event for the Scrum Team only. It is a safe and confidential space where the Scrum Team can openly and honestly reflect on their strengths and weaknesses, and identify actions to improve their performance and collaboration. * The stakeholders are not invited to the Sprint Retrospective. They do not have a say in how the Scrum Team works or what they should improve. The stakeholders can provide feedback and suggestions to the Scrum Team in other events, such as the Sprint Review or the Product Backlog refinement sessions. * The Product Owner is a member of the Scrum Team who is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team. * The Product Owner does not make sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This would violate the self-management and autonomy of the Scrum Team and undermine their trust and empowerment. References: * [Scrum Guide], page 18, section "Sprint Retrospective" * [Scrum Guide], page 7, section "The Scrum Team" * [Scrum Guide], page 17, section "Sprint Review" * [Scrum Guide], page 6, section "Product Owner" * [Scrum Guide], page 10, section "Product Goal"
Question 123
A Scrum Team member should take over both accountabilities Scrum Master and Product Owner.
Correct Answer: A
Question 124
Scrum Teams are allowed to use burn-up charts instead of burn-down charts.
Correct Answer: A
Question 125
What is the timebox for the Sprint Planning event? (choose the best answer)
Correct Answer: C
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 timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences. The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint. Reference: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
