Professional Scrum Master Managing Products with Agility 2 — Questions and Answers
Question 1: A Product Owner notices that stakeholders keep requesting features that were already built but are rarely used. What is the BEST response?
- Remove unused features from the Product Backlog immediately
- Validate feature usage data with stakeholders and use evidence to guide future prioritization (Correct answer)
- Build all requested features since stakeholders know what users need
- Defer all new feature requests until usage improves
Correct answer: Validate feature usage data with stakeholders and use evidence to guide future prioritization
Evidence-based product management means using data on feature usage to have informed conversations with stakeholders rather than blindly accepting or rejecting requests.
Question 2: Which statement BEST describes the relationship between the Product Goal and Sprint Goals?
- Sprint Goals replace the Product Goal once the team starts sprinting
- Sprint Goals are independent objectives set by the Development Team each Sprint
- Sprint Goals are stepping stones that move the Scrum Team toward the Product Goal (Correct answer)
- The Product Goal must be fully achieved before any Sprint Goal is set
Correct answer: Sprint Goals are stepping stones that move the Scrum Team toward the Product Goal
Sprint Goals serve as intermediate milestones that cumulatively advance the team toward the longer-term Product Goal.
Question 3: When should the Product Owner consider splitting a large Product Backlog item?
- Only when the Development Team requests it during Sprint Planning
- When the item cannot be completed within a single Sprint (Correct answer)
- After the Sprint Review reveals the item was too complex
- Only when the item has been in the backlog for more than three Sprints
Correct answer: When the item cannot be completed within a single Sprint
Items that cannot be completed within one Sprint must be split into smaller, Sprint-sized pieces before they can be selected for a Sprint.
Question 4: A competitor releases a disruptive product. How should this affect the Product Backlog?
- Freeze the Product Backlog until a competitive analysis is complete
- Replace the entire Product Backlog to match the competitor's features
- Immediately cancel the current Sprint to respond to the threat
- Re-prioritize the Product Backlog to address the competitive threat while maintaining the Product Goal (Correct answer)
Correct answer: Re-prioritize the Product Backlog to address the competitive threat while maintaining the Product Goal
The Product Backlog is a living artifact that should be updated to reflect new market realities, including competitive threats, while keeping the Product Goal in mind.
Question 5: What is the PRIMARY purpose of Product Backlog refinement?
- To assign tasks to individual developers before the Sprint begins
- To ensure the top Product Backlog items are ready for Sprint Planning (Correct answer)
- To document all stakeholder requirements in detail
- To update the Definition of Done after each Sprint
Correct answer: To ensure the top Product Backlog items are ready for Sprint Planning
Refinement ensures that upcoming Product Backlog items are well-understood and appropriately sized so Sprint Planning can proceed smoothly.
Question 6: How does Scrum support the concept of Minimum Viable Product (MVP)?
- Scrum mandates that teams build an MVP before any full product work begins
- Each Sprint Increment can serve as a potential MVP to gather real market feedback early (Correct answer)
- MVPs are only relevant before Scrum adoption and are replaced by Sprint Goals
- Scrum discourages MVPs because they can create technical debt
Correct answer: Each Sprint Increment can serve as a potential MVP to gather real market feedback early
The iterative nature of Scrum allows teams to release potentially shippable Increments early, which can function as MVPs to validate product direction with real users.
Question 7: A Product Owner wants to maximize value delivered to customers. Which backlog ordering strategy BEST supports this?
- Order items alphabetically to ensure consistent delivery
- Order items by development team preference to optimize flow
- Order items by stakeholder seniority to maintain relationships
- Order items by weighing value delivered against effort required, risk, and dependencies (Correct answer)
Correct answer: Order items by weighing value delivered against effort required, risk, and dependencies
Effective backlog ordering balances multiple factors including customer value, cost of delay, risk, and technical dependencies to maximize overall return.
A Product Owner notices that stakeholders keep requesting features that were already built but are rarely used.
What is the BEST response?