Professional Scrum Master Managing Products with Agility 4 — Questions and Answers
Question 1: What is the Scrum Team's responsibility regarding the Product Goal?
- Only the Product Owner needs to understand the Product Goal
- The entire Scrum Team should understand and work toward the Product Goal (Correct answer)
- The Scrum Master sets the Product Goal independently of the team
- The Product Goal is set by stakeholders and presented to the team as a directive
Correct answer: The entire Scrum Team should understand and work toward the Product Goal
The Product Goal is a commitment for the entire Scrum Team, providing shared purpose and context for all Sprint Goals and Increments.
Question 2: How does value ordering in the Product Backlog differ from simple priority ordering?
- Value ordering considers business value, risk, dependencies, and cost of delay holistically (Correct answer)
- Value ordering means the most expensive features are built first
- Value ordering and priority ordering are identical concepts in Scrum
- Value ordering is determined solely by stakeholder voting
Correct answer: Value ordering considers business value, risk, dependencies, and cost of delay holistically
Value ordering is multi-dimensional, weighing factors like business impact, risk reduction, market opportunity, and the cost of delaying an item.
Question 3: A Product Owner wants to release an Increment before the end of the Sprint. What determines whether this is possible?
- The Scrum Master must approve any mid-Sprint release
- Releases can only happen at Sprint Reviews
- The Definition of Done and the organization's release policies determine when releases can occur (Correct answer)
- All stakeholders must consent before any Increment is released
Correct answer: The Definition of Done and the organization's release policies determine when releases can occur
A Done Increment can be released at any time; the timing is governed by the Definition of Done and organizational or business release decisions, not Scrum events.
Question 4: What role does the Product Owner play in managing technical debt within the Product Backlog?
- Technical debt is solely the Development Team's concern and should not appear in the Product Backlog
- The Product Owner should order technical debt reduction work alongside customer-facing items based on its impact on product value (Correct answer)
- All technical debt must be resolved before new features are added to the backlog
- Technical debt items are automatically removed during Sprint Reviews
Correct answer: The Product Owner should order technical debt reduction work alongside customer-facing items based on its impact on product value
Technical debt impacts the team's ability to deliver value, so the Product Owner must weigh it against feature work and order it appropriately in the Product Backlog.
Question 5: Which of the following is a key characteristic of an effective Product Backlog?
- It is fixed at the start of the project and only updated at major milestones
- It contains only user stories written in a specific template
- It is detailed enough at the top for upcoming Sprints and less detailed further down (Correct answer)
- It must contain an equal number of items for each Sprint
Correct answer: It is detailed enough at the top for upcoming Sprints and less detailed further down
An effective Product Backlog is 'DEEP' — Detailed appropriately, with higher-priority items more refined and lower-priority items remaining at a higher level of abstraction.
Question 6: A Scrum Team has been delivering Increments for six months, but the product has gained no users. What should the Product Owner do FIRST?
- Increase the Sprint velocity to deliver features faster
- Re-examine the Product Goal and validate whether the product is solving a real customer problem (Correct answer)
- Replace the Development Team with more experienced developers
- Extend the Sprint length to allow more features per release
Correct answer: Re-examine the Product Goal and validate whether the product is solving a real customer problem
Low adoption signals a potential product-market fit problem; the Product Owner must revisit the Product Goal and validate assumptions about customer needs before continuing.
Question 7: How should forecasts and roadmaps be treated in a Scrum environment?
- Roadmaps are contractual commitments that the Scrum Team must honor
- Forecasts and roadmaps are planning tools that should be updated as learning occurs and conditions change (Correct answer)
- Scrum prohibits roadmaps because they conflict with agility
- Only the Scrum Master may create and maintain product roadmaps
Correct answer: Forecasts and roadmaps are planning tools that should be updated as learning occurs and conditions change
Roadmaps and forecasts are useful planning tools in Scrum but must be treated as living documents updated through empirical learning, not fixed contracts.
Professional Scrum Master Managing Products with Agility 4
What is the Scrum Team's responsibility regarding the Product Goal?