POPM
Free POPM practice questions
10 questions from our POPM practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Understanding Product Owner/Product Management Roles and Responsibilities
An ART has 9 teams. The Product Owners report that Product Management sends them Features with fixed implementation details and expects them to break the work down without discussion. What is the BEST change to restore an effective PO/PM collaboration?
- AProduct Management focuses on the what and why of Features while Product Owners and teams collaborate on how and on story details Correct answer
- BThe RTE assigns Features to teams based on capacity so that neither Product Management nor the Product Owners have to negotiate scope
- CProduct Management writes all stories as well so that the Product Owners only need to verify that the team follows the specification
- DProduct Owners take over Feature prioritization for their own teams so they are no longer dependent on Product Management decisions
Answer and explanation: In SAFe, Product Management defines the what and why through Features, benefit hypotheses, and acceptance criteria, while Product Owners and teams own the details of stories and implementation, enabling decentralized decisions. Having Product Owners prioritize Features fragments the ART Backlog, having Product Management write every story creates a bottleneck and removes team ownership, and having the RTE assign Features moves content decisions to a role that facilitates rather than owns content.
Question 2 of 10, PI Planning Preparation
The System Architect proposes work to build a new data-streaming platform that future Features will rely on. How should this work appear in the ART Backlog?
- AAs an architectural Enabler Feature, prioritized alongside business Features Correct answer
- BAs a business Feature with a benefit hypothesis stating the expected revenue increase
- CAs hidden work the teams absorb into their stories without telling Product Management
- DAs a separate backlog owned by the System Team that is not visible to Business Owners
Answer and explanation: Enablers capture technical work such as architectural runway and are visible in the ART Backlog, where they are prioritized together with business Features, often with a capacity allocation. Hiding the work or keeping it in a separate invisible backlog destroys transparency, and labelling it a business Feature with a revenue hypothesis misrepresents work that primarily enables future business functionality.
Question 3 of 10, PI Planning Preparation
When applying WSJF with relative estimation across a set of Features, how should Product Management score each Cost of Delay component?
- AScore each Feature in absolute currency so the Cost of Delay reflects the real revenue lost per week
- BScore each column separately with modified Fibonacci numbers, giving the smallest item in that column a 1 Correct answer
- CScore all columns at once for one Feature before moving to the next Feature to keep the context together
- DScore each column from 1 to 100 based on each stakeholder's personal judgment and then average the scores
Answer and explanation: SAFe recommends estimating one WSJF column at a time across all items, using a modified Fibonacci scale, with the smallest item in each column set to 1 so the others are relative to it. Absolute currency values are hard to estimate and unnecessary for sequencing, scoring Feature by Feature loses the relative comparison, and averaging personal 1-100 scores is not the relative technique SAFe describes.
Question 4 of 10, Leadership for PI Planning
At the end of PI Planning, the ART holds a confidence vote and the average is 3, but two team members vote 1. What should happen next?
- AThe RTE records the low votes as accepted risks on the ART planning board for later
- BThe teams with the low votes immediately rework their plans while the other teams leave the event
- CThe plan is accepted because the ART-wide average meets the minimum required score
- DThe people who voted low are invited to share their concerns so they can be addressed Correct answer
Answer and explanation: Low votes should be heard because they often reveal risks or concerns that may require adjustment and can be converted into risks or planning changes. Accepting the plan without listening ignores valuable information, triggering immediate rework before understanding the concern is premature, and recording the votes as accepted risks without discussion skips the conversation that the vote is meant to provoke.
Question 5 of 10, Leadership for PI Planning
Late on day 2, a team discovers that a planned Feature depends on a vendor delivery that will arrive two weeks after the end of the PI. The Feature has the second-highest business value for the ART. What is the BEST response?
- AKeep the Feature committed and plan to finish it in the IP iteration so the original roadmap stays unchanged
- BAssign the Feature to a different team that is less dependent on vendors so that the risk disappears
- CRaise it as an ART PI risk, explore options with Product Management, and update the plan and objectives Correct answer
- DQuietly move the Feature to the next PI without telling Business Owners, to avoid reopening the final plan review
Answer and explanation: New risks discovered late should be made visible as ART PI risks and handled through ROAM, with Product Management exploring options and the plan updated transparently. Committing to work that cannot finish and relying on the IP iteration harms predictability, hiding the change violates transparency, and reassigning the Feature does not remove the vendor dependency.
Question 6 of 10, Iteration Execution
A Product Owner is reviewing a story that requires front-end, API, and database changes and would take most of the iteration. Which practice from the INVEST model is the Product Owner trying to restore by splitting it into smaller vertical slices?
- AEstimable
- BSmall Correct answer
- CValuable
- DIndependent
Answer and explanation: The S in INVEST means stories should be small enough to complete within an iteration, and splitting vertically keeps each slice valuable while reducing size. Valuable means each story delivers value to a user, Independent means minimal dependencies between stories, and Estimable means the team understands it well enough to size it; none of these is the main concern with an oversized story.
Question 7 of 10, Iteration Execution
In the iteration retrospective, the team notes that stories frequently fail acceptance because the Product Owner's expectations were unclear. Which improvement BEST addresses the root cause?
- AHave the Scrum Master/Team Coach accept stories on the Product Owner's behalf so acceptance happens faster
- BIncrease the team's story-point estimates by a buffer so rework caused by unclear stories fits into the iteration
- CLet the Product Owner accept stories at the end of the PI instead of during the iteration so more feedback can be gathered
- DDefine acceptance criteria collaboratively with the Product Owner and testers before stories enter an iteration Correct answer
Answer and explanation: Agreeing on acceptance criteria together before work starts, for example with the three amigos approach, removes ambiguity at the source. Delaying acceptance until the end of the PI creates large batches of unvalidated work, having the Scrum Master/Team Coach accept stories removes the Product Owner's content authority, and padding estimates hides the problem rather than fixing it.
Question 8 of 10, Iteration Execution
A team wants to deploy code to production but keep a new capability hidden from customers until marketing is ready. Which technique allows this?
- AA canary release to all users
- BA hardening iteration before launch
- CA dark launch using feature toggles Correct answer
- DA blue/green database migration
Answer and explanation: A dark launch deploys functionality to production while keeping it invisible to users, typically controlled by feature toggles, so release can happen later on business demand. A canary release exposes the change to a subset of users, blue/green environments switch traffic between environments, and a hardening iteration delays deployment rather than separating it from release.
Question 9 of 10, PI Execution
An ART wants to ensure the System Demo reflects real progress. Which approach BEST supports this?
- APostponing the demo until the final iteration when all Features are complete
- BHaving each team demo its stories separately on local development machines
- CDemonstrating the integrated work of all teams in a staging environment Correct answer
- DShowing slides that summarize each team's completed stories and velocity
Answer and explanation: The System Demo shows the fully integrated increment from all teams, ideally in a staging environment that resembles production. Separate team demos on local machines hide integration problems, slides do not show working software, and waiting until the end of the PI removes the frequent objective evidence that SAFe principle 5 relies on.
Question 10 of 10, Apply AI to Product Roles
An ART wants to introduce an AI assistant that drafts Features from customer feedback. Leaders worry about quality, data privacy, and accountability. Which approach BEST addresses these concerns?
- ABan the tool until it achieves complete accuracy, because any errors in drafted Features would harm customers
- BLet the AI publish Features directly to the ART Backlog, and have teams reject the poor ones during PI Planning
- CAllow each Product Manager to choose any public tool, since individual judgment is enough to manage all of the privacy risks
- DUse an approved tool, define guidelines for data use, and keep Product Management accountable for reviewing every draft Correct answer
Answer and explanation: Responsible adoption combines approved tools, clear data guidelines, and human accountability for AI-assisted work products. Unrestricted public tools create privacy risk, waiting for perfect accuracy is unrealistic and forgoes benefits, and publishing AI drafts directly pushes quality control onto PI Planning, where it is far more costly.