Agile Business Analysis FREE Agile Business Analysis Product Backlog Management Questions and Answers 2 — Questions and Answers
Question 1: A Product Owner notices that several backlog items have been sitting untouched for over six sprints. What is the most appropriate action?
- Archive or remove the stale items after confirming they are no longer relevant (Correct answer)
- Automatically move them to the top of the backlog
- Assign them to the next available sprint regardless of priority
- Split each item into smaller stories to make them easier to complete
Correct answer: Archive or remove the stale items after confirming they are no longer relevant
Stale backlog items that no longer align with product goals should be removed or archived to keep the backlog lean and relevant.
Question 2: Which technique is most effective for ordering a large product backlog when multiple stakeholders have competing priorities?
- Weighted Shortest Job First (WSJF) (Correct answer)
- Alphabetical ordering by epic name
- First-come, first-served based on request date
- Random selection to ensure fairness
Correct answer: Weighted Shortest Job First (WSJF)
WSJF considers cost of delay and job size to objectively prioritize items that deliver the highest economic value first.
Question 3: What is the primary purpose of a backlog refinement session?
- To ensure upcoming backlog items are well-understood, estimated, and ready for sprint planning (Correct answer)
- To assign all backlog items to specific developers
- To get stakeholder sign-off on completed work
- To create the sprint goal for the next iteration
Correct answer: To ensure upcoming backlog items are well-understood, estimated, and ready for sprint planning
Backlog refinement ensures items near the top of the backlog have clear acceptance criteria, estimates, and sufficient detail for the team to commit to them.
Question 4: A business analyst discovers that a high-priority user story has unclear acceptance criteria two days before sprint planning. What should they do first?
- Collaborate with the Product Owner and stakeholders to clarify and document the acceptance criteria immediately (Correct answer)
- Remove the story from the backlog until the next refinement session
- Ask the development team to estimate it anyway and clarify during the sprint
- Postpone sprint planning until all stories are fully defined
Correct answer: Collaborate with the Product Owner and stakeholders to clarify and document the acceptance criteria immediately
Proactively clarifying acceptance criteria before sprint planning ensures the team can make informed commitments without delays.
Question 5: In an agile context, what does the acronym DEEP represent when describing a well-maintained product backlog?
- Detailed appropriately, Estimated, Emergent, Prioritized (Correct answer)
- Defined, Evaluated, Executed, Published
- Documented, Estimated, Enclosed, Planned
- Detailed, Expanded, Enumerated, Packaged
Correct answer: Detailed appropriately, Estimated, Emergent, Prioritized
A DEEP backlog has items that are detailed appropriately based on priority, estimated, emergent to reflect evolving understanding, and prioritized by value.
Question 6: When should a Product Owner consider splitting a large product backlog item?
- When the item is too large to be completed within a single sprint and needs to deliver incremental value (Correct answer)
- Only after the development team has attempted and failed to complete it
- At the end of the release cycle during a retrospective
- When the Scrum Master requests it during the daily standup
Correct answer: When the item is too large to be completed within a single sprint and needs to deliver incremental value
Large items should be split before they enter a sprint so each piece can deliver value independently within one iteration.
Agile Business Analysis FREE Agile Business Analysis Product Backlog Management Questions and Answers 2
A Product Owner notices that several backlog items have been sitting untouched for over six sprints.
What is the most appropriate action?