.png&w=3840&q=75)
Question bank
Advanced Certified Scrum Product Owner (A-CSPO)
41 Advanced Certified Scrum Product Owner (A-CSPO) questions with the correct answer and a written explanation, organised across 6 exam domains.
- 41 questions
- 6 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Agile Coaching
4 questions in this domain
- Question 1Single Choice
According to the playbook, what is the primary focus of a Product Owner's mentoring of developers?
- ATeaching the team to understand market trends, customer pain points, and the competitive landscapeCorrect answer
- BAssigning technical coding tasks to developers
- CTracking sprint velocity and story counts
- DWriting exhaustive requirement documents
Why this is the answer
The PO mentors the team on business literacy, enabling informed decisions that support long-term product strategy.
- Question 2Multiple Select
Which of the following are key concepts of Agile mentoring for a Product Owner? Select all that apply.
- AValue-Driven MindsetCorrect answer
- BCollaborative RefinementCorrect answer
- CShared Product OwnershipCorrect answer
- DDocumentation Overload Fallacy
Why this is the answer
The key concepts include business literacy empowerment, value-driven mindset, collaborative refinement, shared product ownership, and strategic alignment.
- Question 3Interactive
Analyze the code block and identify the common trap the team is demonstrating.
- AThe Feature Factory FallacyCorrect answer
- BMistaking User Feedback for User Requirements
- COver-engineering the Experiment
- DThe Manager Trap
Why this is the answer
The snippet describes high velocity and many completed items without validating business value, which is the Feature Factory Fallacy.
- Question 4Single Choice
In the context of Product Owner mentoring, what does the 'Manager Trap' refer to?
- AAssigning tasks to developers and telling them how to codeCorrect answer
- BConfusing process-based mentoring with value-based mentoring
- CProviding exhaustive documentation to build understanding
- DRelying only on user feedback for requirements
Why this is the answer
The Manager Trap occurs when the PO mentors by assigning tasks or dictating how developers should code, violating self-management.
Backlog Management
10 questions in this domain
- Question 5Single Choice
According to the playbook, which behavior best demonstrates Business Literacy Empowerment by a Product Owner?
- AMentor the team to understand market trends, customer pain points, and the competitive landscape.Correct answer
- BAssign development tasks to individual team members.
- CInstruct developers on the exact coding patterns to use.
- DProvide extensive requirement documents for each backlog item.
Why this is the answer
Business Literacy Empowerment is about teaching the team market trends, customer pain points, and the competitive landscape so they can make informed technical decisions in support of long-term strategy.
- Question 6Multiple Select
Which of the following statements are true about Shared Product Ownership, according to the playbook? Select all that apply.
- AThe Product Owner remains accountable for the product's success.Correct answer
- BThe Product Owner guides the team to take interest in product metrics and customer feedback.Correct answer
- CDevelopers are ultimately accountable for the product's success.
- DThe team should not concern itself with customer feedback.
Why this is the answer
In Shared Product Ownership, accountability remains with the Product Owner, but the PO guides the team to care about product metrics and customer feedback, fostering a culture where everyone feels responsible for the product's success.
- Question 7Interactive
Review the code snippet. Which common mentoring trap is the Product Owner demonstrating?
- AManager TrapCorrect answer
- BScrum Master Confusion Trap
- CDocumentation Overload Trap
- DFeature Factory Fallacy
Why this is the answer
The snippet shows a Product Owner assigning tasks and telling developers how to code. This is the Manager Trap, which violates the self-management principle of Scrum.
- Question 8Single Choice
According to the playbook, how does Product Owner mentoring differ from Scrum Master mentoring?
- AThe PO mentors on value; the SM mentors on process.Correct answer
- BThe PO mentors on process; the SM mentors on value.
- CThe PO mentors on velocity; the SM mentors on ROI.
- DThe PO and SM both focus exclusively on ceremonies.
Why this is the answer
The Scrum Master Confusion Trap warns against confusing process-based mentoring with value-based mentoring. The PO mentors on value, market fit, and ROI, while the SM mentors on Scrum ceremonies and velocity.
- Question 9Multiple Select
Which actions align with the Value-Driven Mindset described in the playbook? Select all that apply.
- ATeach the team to evaluate work through the lens of business value.Correct answer
- BShow the team how specific user stories contribute to the overall Product Goal.Correct answer
- CUse completed story count as the primary indicator of success.
- DAvoid discussing business value during backlog refinement.
Why this is the answer
A Value-Driven Mindset moves the team from a 'feature factory' mentality by teaching them to evaluate work through business value and see how user stories connect to the Product Goal.
- Question 10Interactive
The code snippet represents the Product Owner's approach to mentoring. Which trap is being used?
- ADocumentation Overload TrapCorrect answer
- BManager Trap
- CScrum Master Confusion Trap
- DShared Product Ownership
Why this is the answer
Providing exhaustive, detailed requirement documents is the Documentation Overload Trap. True mentoring builds the team's capacity to understand intent rather than drowning them in documentation.
- Question 11Single Choice
In collaborative refinement, what is the Product Owner trying to build in the team?
- ADecompose complex epics into actionable, valuable increments independently.Correct answer
- BWait for the Product Owner to break down every requirement.
- CIncrease velocity by skipping backlog refinement.
- DEnsure all items are documented in exhaustive detail.
Why this is the answer
Collaborative Refinement is about teaching the team to engage deeply with the backlog and decompose complex epics into actionable, valuable increments independently.
- Question 12Multiple Select
Which behaviors support Strategic Alignment as described in the playbook? Select all that apply.
- AHelp the team connect daily tactical work to high-level organizational objectives.Correct answer
- BFrame technical debt discussions in the context of long-term product agility and value delivery.Correct answer
- CKeep daily work completely separate from organizational strategy.
- DAvoid architectural spikes because they delay tactical work.
Why this is the answer
Strategic Alignment means helping the team see the link between daily work and organizational objectives, and framing technical debt and architectural spikes within the context of long-term product agility and value delivery.
- Question 13Interactive
The code block below describes a mentoring focus. Which trap occurs when the Product Owner adopts this focus instead of value-based mentoring?
- AScrum Master Confusion TrapCorrect answer
- BManager Trap
- CDocumentation Overload Trap
- DValue-Driven Mindset
Why this is the answer
The snippet focuses on velocity, ceremonies, and story points—process-based mentoring. The Scrum Master Confusion Trap occurs when this is confused with the value-based mentoring a Product Owner should provide.
- Question 14Single Choice
Which statement best describes the 'Feature Factory' fallacy from the playbook?
- AAssuming that a high velocity or a large number of completed User Stories indicates success.Correct answer
- BTaking too much time to build high-fidelity prototypes for every experiment.
- CMistaking user feedback for user requirements.
- DAssigning features to developers instead of letting the team self-manage.
Why this is the answer
The Feature Factory Fallacy is assuming that high velocity or a large number of completed User Stories means the team is delivering value. A value-driven mindset focuses on business outcomes instead.
Metrics and Reporting
4 questions in this domain
- Question 15Single Choice
What is the primary focus of value-driven mentoring for a Product Owner?
- AMoving the team from a 'feature factory' mentality to a value-oriented approachCorrect answer
- BIncreasing sprint velocity at all costs
- CProviding exhaustive requirement documents
- DAssigning coding tasks to developers
Why this is the answer
Value-driven mentoring shifts the team from merely producing features to evaluating work through business value and contribution to the Product Goal.
- Question 16Multiple Select
Which of the following are common traps in Product Owner mentoring? Select all that apply.
- AMistaking user feedback for user requirementsCorrect answer
- BAssuming high velocity or many completed User Stories indicates business valueCorrect answer
- COver-engineering the experiment by building a high-fidelity prototype for a simple conceptCorrect answer
- DFostering shared product ownership across the team
Why this is the answer
The traps include confusing feedback with requirements, the Feature Factory Fallacy, and over-engineering experiments. Shared product ownership is a positive mentoring goal.
- Question 17Interactive
Review the dashboard metrics in the code block. Which common trap is being illustrated?
- AThe Feature Factory FallacyCorrect answer
- BMistaking user feedback for user requirements
- CThe Documentation Overload Trap
- DThe Manager Trap
Why this is the answer
Celebrating completed stories and velocity without considering customer impact reflects the Feature Factory Fallacy: output is mistaken for value.
- Question 18Single Choice
According to the playbook, what does true mentoring build in the team?
- AThe team's capacity to understand the intent behind their workCorrect answer
- BDependence on exhaustive, detailed requirement documents
- CReliance on the Product Owner for every technical decision
- DA focus on process metrics such as velocity over business value
Why this is the answer
True mentoring builds the team's capacity to understand intent and engage in Product Backlog Refinement, rather than requiring detailed documentation or task assignment.
Product Vision
8 questions in this domain
- Question 19Single Choice
Which concept refers to a Product Owner mentoring the team to understand market trends, customer pain points, and the competitive landscape?
- ABusiness Literacy EmpowermentCorrect answer
- BValue-Driven Mindset
- CCollaborative Refinement
- DStrategic Alignment
Why this is the answer
Business Literacy Empowerment means teaching the team about market trends, customer pain points, and the competitive landscape so they can align technical decisions with product strategy.
- Question 20Multiple Select
Which statements accurately reflect the 'Feature Factory' fallacy?
- AAssuming that high velocity or a large number of completed User Stories indicates product valueCorrect answer
- BTreating output as the primary measure of success instead of outcomesCorrect answer
- CFocusing on validating hypotheses through experiments
- DAligning every sprint goal with the Product Goal
Why this is the answer
The Feature Factory fallacy assumes that velocity or story count equals value. It treats output as success instead of focusing on business outcomes and validated learning.
- Question 21Interactive
The code block shows a Product Owner describing a mentoring activity. Which common trap is illustrated?
- ADocumentation Overload TrapCorrect answer
- BManager Trap
- CScrum Master Confusion Trap
- DShared Product Ownership
Why this is the answer
Providing exhaustive, detailed requirement documents is not real mentoring. The Documentation Overload Trap occurs when the PO relies on documents instead of building the team's capacity to understand intent.
- Question 22Single Choice
Which trap occurs when a Product Owner acts as a manager by assigning tasks and telling developers how to code?
- AManager TrapCorrect answer
- BScrum Master Confusion Trap
- CDocumentation Overload Trap
- DValue-Driven Mindset
Why this is the answer
The Manager Trap assumes the PO mentors by assigning tasks or telling developers how to code, which violates the team's self-management principle.
- Question 23Multiple Select
Which mentoring topics belong to the Product Owner's value-based mentoring, not the Scrum Master's process-based mentoring?
- ATeaching the team to evaluate ROI and market fitCorrect answer
- BHelping the team understand customer feedback and Product Goal contributionCorrect answer
- CCoaching the team on the length of Sprint events
- DGuiding the team on velocity and Scrum ceremony mechanics
Why this is the answer
The PO mentors on value, including ROI, market fit, customer feedback, and Product Goal contribution. The Scrum Master mentors on process, such as ceremonies and velocity.
- Question 24Interactive
The code block shows a common Product Owner trap. What is it?
- AMistaking 'User Feedback' for 'User Requirements'Correct answer
- BOver-engineering the Experiment
- CFeature Factory Fallacy
- DDocumentation Overload Trap
Why this is the answer
Feedback is about observing behavior and reaction. Writing a story based only on a stated request, without observing behavior, confuses user feedback with a validated user requirement.
- Question 25Single Choice
According to Collaborative Refinement, what is the PO mentoring the team to do?
- ADecompose complex epics into actionable, valuable increments independentlyCorrect answer
- BWait for the PO to provide prebroken requirements
- CFocus only on technical estimates during refinement
- DAvoid refining the backlog until the Sprint begins
Why this is the answer
Collaborative Refinement builds the team's ability to decompose complex epics into actionable, valuable increments on their own, rather than depending on hand-down requirements.
- Question 26Multiple Select
Which practices demonstrate Shared Product Ownership?
- ATeam members review product metrics and customer feedbackCorrect answer
- BEveryone feels responsible for the product's successCorrect answer
- CPO assigns all backlog tasks
- DDevelopers wait for the PO to make every product decision
Why this is the answer
Shared Product Ownership encourages the team to take interest in product metrics and customer feedback, fostering a culture where everyone feels responsible for the product's success.
Release Planning
7 questions in this domain
- Question 27Single Choice
Which mentoring concept involves teaching the team about market trends, customer pain points, and the competitive landscape?
- ABusiness Literacy EmpowermentCorrect answer
- BValue-Driven Mindset
- CThe Manager Trap
- DDocumentation Overload Trap
Why this is the answer
Business Literacy Empowerment focuses on market trends, customer pain points, and competitive landscape to support strategic decisions.
- Question 28Multiple Select
Which actions reflect mentoring for shared product ownership? (Select all that apply.)
- AEncouraging the team to monitor product metrics and customer feedbackCorrect answer
- BGuiding the team to feel responsible for product successCorrect answer
- CAssigning development tasks to individual team members
- DTelling developers exactly how to implement code
Why this is the answer
Shared ownership means the team cares for metrics and feedback and feels responsible for success, not assigning tasks or dictating code.
- Question 29Interactive
Review the code block. Which common trap is the Product Owner demonstrating?
- AThe Manager TrapCorrect answer
- BThe Scrum Master Confusion Trap
- CThe Documentation Overload Trap
- DStrategic Alignment
Why this is the answer
Assigning tasks or telling developers how to code violates self-management and exemplifies the Manager Trap.
- Question 30Single Choice
In Scrum, the Product Owner mentors the team on value, while the Scrum Master mentors the team on what?
- AProcessCorrect answer
- BROI
- CMarket fit
- DTechnical debt
Why this is the answer
The PO mentors on value; the SM mentors on process, such as ceremonies and velocity.
- Question 31Multiple Select
Which indicators show a value-driven mindset instead of a feature-factory mentality? (Select all that apply.)
- AEvaluating user stories by contribution to the Product GoalCorrect answer
- BConnecting work to ROI and market fitCorrect answer
- CMeasuring success by number of completed stories
- DPrioritizing output over outcomes
Why this is the answer
Value-driven mindset focuses on business value and product goal, not high velocity or story counts.
- Question 32Interactive
Read the code block. Which common trap is represented?
- ADocumentation Overload TrapCorrect answer
- BManager Trap
- CScrum Master Confusion Trap
- DFeature Factory Fallacy
Why this is the answer
Providing exhaustive requirements is not mentoring; true mentoring builds capacity to understand intent.
- Question 33Single Choice
What is the key difference between user feedback and user requirements?
- AFeedback is observing behavior and reaction; requirements are stated needsCorrect answer
- BFeedback is a written list of features; requirements are behavioral observations
- CFeedback and requirements are identical
- DFeedback is only collected after release; requirements are collected during sprint
Why this is the answer
User feedback is about observing behavior and reaction, not treating comments as a requirement specification.
Stakeholder Management
8 questions in this domain
- Question 34Single Choice
What does business literacy empowerment enable developers to do?
- AInformed technical decisions aligned with strategyCorrect answer
- BFocus only on sprint goals
- CIgnore customer feedback
- DDelegate decisions to stakeholders
Why this is the answer
Business literacy lets developers connect their technical work to long-term product strategy, not just sprint goals. This supports sustainable value delivery.
- Question 35Multiple Select
Which two statements accurately describe a value-driven mindset in Scrum? (Choose two)
- AShift from feature factory to value orientationCorrect answer
- BEvaluate work through business valueCorrect answer
- CMaximize features delivered per sprint
- DIgnore the Product Goal
Why this is the answer
A value-driven mindset shifts the team away from feature output and toward business value, tying work to the Product Goal.
- Question 36Interactive
The code block shows a Product Owner's mentoring action. Which Scrum trap is represented?
- AManager TrapCorrect answer
- BScrum Master Confusion Trap
- CDocumentation Overload Trap
- DFeature Factory Fallacy
Why this is the answer
Assigning coding tasks violates self-management and reflects the Manager Trap, where the PO instructs developers how to code.
- Question 37Single Choice
What is collaborative refinement intended to build in the team?
- ADecompose epics into valuable incrementsCorrect answer
- BCreate exhaustive requirement documents
- CDelegate refinement to stakeholders
- DIncrease velocity at all costs
Why this is the answer
Collaborative refinement builds the team's ability to break down complex epics into valuable increments on their own.
- Question 38Multiple Select
Which two statements accurately describe shared product ownership? (Choose two)
- APO remains accountableCorrect answer
- BTeam values metrics and feedbackCorrect answer
- CDevelopers hold sole accountability
- DTeam avoids product outcomes
Why this is the answer
In shared ownership, accountability stays with the PO, while the team is empowered to care about metrics and customer feedback.
- Question 39Interactive
The code block describes a Product Owner's mentoring focus. Which trap is this?
- AScrum Master Confusion TrapCorrect answer
- BManager Trap
- CDocumentation Overload Trap
- DFeature Factory Fallacy
Why this is the answer
Focusing on velocity and ceremonies is process-based mentoring, which is the Scrum Master's role, not the PO's.
- Question 40Single Choice
What context does strategic alignment provide for technical debt discussions and architecture spikes?
- ASustaining long-term agility and value deliveryCorrect answer
- BCompleting sprint tasks
- CEliminating all technical debt
- DSatisfying developer preferences
Why this is the answer
Strategic alignment ensures technical decisions are framed around long-term agility and value delivery, not short-term focus.
- Question 41Multiple Select
Which two items are recognized common traps in Product Owner mentoring? (Choose two)
- AMistaking feedback for requirementsCorrect answer
- BAssuming velocity equals valueCorrect answer
- CEncouraging backlog refinement
- DEmpowering shared ownership
Why this is the answer
The playbook identifies mistaking feedback for requirements and the feature factory fallacy as common traps.
Frequently asked questions
Everything about the Advanced Certified Scrum Product Owner (A-CSPO) question bank and how to use it.