What does it mean for a team to be a "cross-functional" Team?
Correct Answer: B
Question 57
True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.
Correct Answer: B
Explanation * In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value. * Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities. Therefore, a Product Owner with multiple teams working on one product should not maintain separate Product Backlogs for each team. * 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. * In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums. References: * Scrum Guide: https://www.scrumguides.org/scrum-guide.html * Nexus: [1] * LeSS: [2] * SAFe: [3] * Scrum of Scrums: [4]
Question 58
The length of a Sprint should be: (choose the best answer)
Correct Answer: D
The length of a Sprint is the timebox within which the Scrum Team creates a potentially releasable product Increment. The Sprint is a container for all the other Scrum events, such as the Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. The Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process. The length of a Sprint should be no more than one calendar month. This is the maximum duration allowed by Scrum, as longer Sprints can increase the complexity and risk of the product development. Longer Sprints can also reduce the agility and responsiveness of the Scrum Team to changing customer needs and market conditions. The length of a Sprint should also be short enough to keep the business risk acceptable to the Product Owner. 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 length of a Sprint affects how frequently and effectively the Product Owner can validate, verify, and deliver value to the customers and users. The length of a Sprint should also be short enough to be able to synchronize the development work with other business events. The Scrum Team operates within a broader organizational context that may have other events, cycles, or deadlines that affect or depend on product development. For example, there may be marketing campaigns, sales promotions, regulatory compliance, or contractual obligations that require coordination and alignment with the product delivery. The length of a Sprint affects how well and timely the Scrum Team can synchronize their work with these other business events. Reference: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Question 59
True or False: A Product Owner should measure product value by the increase in the team's velocity.
Correct Answer: B
Explanation A Product Owner should not measure product value by the increase in the team's velocity. This is because: * Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done. * Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good. * Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals. * A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data, market share, return on investment, or social impact. References: * [Scrum Guide], page 7, section "Developers" * [Scrum Guide], page 10, section "Definition of Done" * [Scrum Guide], page 15, section "Sprint Backlog" * [Professional Scrum Product Owner Training], page 5, section "Product Value" * [Professional Scrum Product Owner Training], page 9, section "Business Strategy"
Question 60
What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team? (choose the best three answers)
Correct Answer: C,D,E
The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are: * It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and focus on delivering value that contributes to the product vision. * It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to work on. It helps the Scrum Team prioritize and optimize their work based on value and impact. * It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress towards the Product Goal. Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a Product Goal is or how Scrum works. References: * [Scrum Guide], page 10, section "Product Goal" * [Professional Scrum Product Owner™ Training], page 6, section "Product Vision" * [Professional Scrum Product Owner™ Training], page 7, section "Product Backlog Management" * [Scrum Guide], page 13, section "Sprint Review" * [Scrum Guide], page 10, section "Increment"
