Agile Business Analysis Product Backlog Management 5 — Questions and Answers
Question 1: What is the consequence of a Product Owner delegating all backlog ordering decisions to the development team?
- The team delivers faster because they choose their preferred work
- Business value alignment weakens because the team may optimize for technical preference (Correct answer)
- Stakeholders gain more visibility into the backlog
- The Scrum Master must assume the Product Owner role
Correct answer: Business value alignment weakens because the team may optimize for technical preference
The PO's accountability for business value is lost when ordering is fully delegated, risking a technically-driven backlog that misses strategic goals.
Question 2: In a Kanban-influenced backlog management approach, what limits the number of items the team works on simultaneously?
- The Product Owner's approval
- Work-in-Progress (WIP) limits (Correct answer)
- The sprint length
- Story point estimates
Correct answer: Work-in-Progress (WIP) limits
WIP limits constrain the number of items in each workflow stage, reducing multitasking and improving flow through the system.
Question 3: A Product Owner is managing a backlog for a product used by both internal employees and paying customers. How should stakeholder influence on backlog ordering be balanced?
- Paying customers always take precedence over internal users
- The PO weighs business value, risk, and strategic goals across all user groups (Correct answer)
- Internal employees set priorities since they use the product daily
- Backlog order is decided by majority vote among stakeholders
Correct answer: The PO weighs business value, risk, and strategic goals across all user groups
The PO must holistically evaluate business value, risk reduction, and strategic alignment rather than defaulting to any single stakeholder group.
Question 4: What is the purpose of a 'walking skeleton' in product backlog management?
- A minimal end-to-end implementation that validates the system's key architecture early (Correct answer)
- A backlog of only bug fixes and defects
- A visual roadmap of all planned backlog items
- A template for writing user stories
Correct answer: A minimal end-to-end implementation that validates the system's key architecture early
A walking skeleton is a thin end-to-end slice of the system that proves the architecture works, informing backlog decisions early.
Question 5: Which practice helps prevent 'scope creep' in product backlog management?
- Avoiding sprint reviews to reduce stakeholder contact
- Maintaining a clear product vision and rigorously evaluating new items against it (Correct answer)
- Locking the backlog at project start and allowing no changes
- Having the development team reject all new requirements
Correct answer: Maintaining a clear product vision and rigorously evaluating new items against it
A strong product vision serves as a filter — new items that don't align with it can be deprioritized or rejected with clear rationale.
Question 6: What is the key difference between a product backlog and a sprint backlog?
- The product backlog is owned by the Scrum Master; the sprint backlog by the team
- The product backlog contains all future work; the sprint backlog contains only work selected for the current sprint (Correct answer)
- The product backlog is fixed; the sprint backlog changes constantly
- The product backlog contains only features; the sprint backlog contains only bugs
Correct answer: The product backlog contains all future work; the sprint backlog contains only work selected for the current sprint
The product backlog is the comprehensive ordered list of all desired product work, while the sprint backlog is the subset selected for a single sprint.
Question 7: How should a Product Owner handle technical debt items in the product backlog?
- Keep all technical debt in a separate backlog invisible to stakeholders
- Include technical debt as explicit backlog items, prioritized alongside feature work (Correct answer)
- Assign all technical debt to developers to resolve independently
- Defer all technical debt until after the product launch
Correct answer: Include technical debt as explicit backlog items, prioritized alongside feature work
Making technical debt visible in the product backlog allows the PO and stakeholders to make informed trade-off decisions about when to address it.
Agile Business Analysis Product Backlog Management 5
What is the consequence of a Product Owner delegating all backlog ordering decisions to the development team?