IIBA-CPOA · IIBA · Product Ownership Practices · Bank updated 2026-07-02
IIBA-CPOA practice questions: Product Ownership Practices
5 free questions from 76 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Product Ownership Practices section of our IIBA-CPOA bank (76 questions on this area). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Product Ownership Practices
An organization splits product ownership across three people: one writes the vision, one orders the backlog, and one approves completed work. The team frequently receives conflicting priority signals and wastes time reconciling them. Which corrective principle of product ownership practice most directly addresses this problem?
AHave the development team independently decide priorities when the three disagree.
BRotate the three product owners weekly so each takes a turn directing the team.
CEstablish a single product owner who holds final say over backlog ordering to avoid conflicting direction.
DAdd a fourth coordinator role to mediate between the three product owners.
Show answer & explanation
C is correct. Effective product ownership requires a single point of accountability for the product backlog. Fragmenting the role across multiple people produces conflicting priorities. The fix is to designate one product owner with final authority over backlog ordering, not to add coordinators, rotate the role, or hand prioritization to the team.
↗ IIBA Product Ownership Analysis guidance — Product Ownership Practices
2/5 · Product Ownership Practices · hard
A product owner has a story: 'As a user, I can pay by credit card, PayPal, and bank transfer so I can check out.' It is too large for one iteration. The product owner wants to split it so each resulting story still delivers usable, end-to-end value to a customer rather than producing a non-shippable technical layer. Which split best honors that principle?
ASplit into 'happy path' and 'all error handling', releasing the happy path alone to production
BSplit into 'design the payment UI', 'build the payment service', and 'write the payment database layer'
CSplit by payment method, e.g. 'pay by credit card', then 'pay by PayPal', then 'pay by bank transfer', each independently shippable
DKeep the story whole but assign three developers to work the layers in parallel within one iteration
Show answer & explanation
C is correct. Good story splitting creates thin vertical slices, each delivering usable end-to-end value and independently releasable, consistent with INVEST. Splitting a multi-method payment story by payment method achieves this. Splitting by technical layer or carving off all error handling produces non-shippable fragments, and adding developers does not split the story at all.
↗ IIBA Product Ownership Analysis guidance — Product Ownership Practices
3/5 · Product Ownership Practices · hard
A product owner forwards every developer question to a business sponsor and merely transcribes whatever decisions the sponsor returns, holding no view of value and deferring all prioritization upward. Delivery slows because each question waits days for a reply, and the backlog drifts from product objectives. Which characterization of this product owner's behavior is most accurate, and what should change?
AThe product owner is correctly protecting the business by routing all decisions to the most senior sponsor
BThe product owner is acting as a proxy or scribe rather than an empowered decision-maker, and should be enabled to own prioritization and make value-based decisions within agreed boundaries
CThe slowdown is simply a capacity problem; adding developers will resolve it
DThe team should bypass the product owner and take requirements directly from the sponsor to remove the bottleneck
Show answer & explanation
B is correct. A product owner who only forwards questions and transcribes others' decisions, with no value perspective or authority, exhibits the proxy or scribe anti-pattern. It causes decision latency and backlog drift. The remedy is empowerment: the product owner should hold a clear view of value, own prioritization, and decide promptly within agreed boundaries, escalating only true exceptions, rather than being bypassed or treated as a staffing problem.
↗ IIBA Product Ownership Analysis guidance — Product Ownership Practices
4/5 · Product Ownership Practices · hard
A product owner has a story 'As a customer I can check out and pay' that is far too large for one sprint and bundles cart review, address entry, multiple payment methods, and order confirmation. The product owner wants each resulting slice to still deliver an independently demonstrable, end-to-end, vertically thin piece of value rather than a horizontal technical layer. Which split is most consistent with INVEST and value-delivering vertical slicing?
AKeep the story whole but add many acceptance criteria so the team can pace itself within the sprint
BSplit by technical layer — one story for the database schema, one for the API, one for the UI
CSplit by workflow steps and variations — e.g., 'pay with a single saved card' first, then add address entry, additional payment methods, and confirmation as separate stories
DSplit by team role — one story for the developers, one for the testers, one for the designer
Show answer & explanation
C is correct. Effective story splitting (as in patterns like SPIDR — Spike, Paths, Interfaces, Data, Rules) produces vertically thin, independently demonstrable slices that each deliver end-to-end value. Splitting by workflow steps and variations does this; splitting by technical layer or team role creates horizontal fragments that demonstrate no standalone value, and adding acceptance criteria does not make a story smaller.
↗ IIBA Product Ownership Analysis guidance — Product Ownership Practices
5/5 · Product Ownership Practices · hard
Two backlog features require identical development effort, but Feature X's value decays sharply the longer it is delayed (for example, it supports a seasonal promotion), while Feature Y's value stays essentially flat over time. Applying Cost of Delay reasoning to sequence a single-threaded backlog, what should the product owner conclude?
AFeature Y should be sequenced first, because a flat value curve indicates it has higher lifetime value than a decaying one
BFeature X should be sequenced first, because its steep urgency profile means delaying it destroys more value per unit of time than delaying Feature Y
CCost of Delay cannot be applied in this situation because the two features have identical development effort
DBoth features should be split in half and delivered in parallel regardless of team capacity, since Cost of Delay only affects estimation, not sequencing
Show answer & explanation
B is correct. Cost of Delay quantifies the economic impact of postponing a piece of work. When development effort is equal, the feature whose value decays fastest if delayed should be sequenced first to minimize lost value overall, which is the underlying economic logic behind Weighted Shortest Job First sequencing.
↗ IIBA Product Ownership Analysis guidance — Product Ownership Practices
Other IIBA-CPOA areas
The same kind of free sample for every other section of the IIBA-CPOA bank:
Study Product Ownership Practices with instant feedback
6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.
Create your free account →
Read next
ECBA vs CCBA vs CBAP: Which IIBA Certification Fits Your Experience Level? (2026)
ECBA, CCBA or CBAP? The eligibility gate that picks for you, what the 2026 ECBA rewrite changed, and each credential's three-year cost, verified against IIBA.
PMI-PBA vs CBAP: The Business Analysis Certification Decision, Settled with Data
PMI-PBA ($405-555, 36 months of experience) vs CBAP ($495-650 all-in, 7,500 hours plus references): eligibility, exam mechanics, three-year cost, salary data.
ExamDeck is an independent study tool, not affiliated with IIBA®. IIBA-CPOA and BABOK® are trademarks of the International Institute of Business Analysis. Exam facts checked against official IIBA materials (as of August 2026); confirm current details on iiba.org.