Agile Business Analysis Product Backlog Management 3 — Questions and Answers
Question 1: Which of the following BEST describes the concept of a 'ready' product backlog item?
- It has been approved by the Product Owner and stakeholders
- It is small enough to complete in one sprint, clearly understood, and estimated (Correct answer)
- It has been coded and unit-tested by a developer
- It has a formal business case document attached
Correct answer: It is small enough to complete in one sprint, clearly understood, and estimated
A 'ready' PBI meets the Definition of Ready: small, understandable, estimated, and actionable within a sprint.
Question 2: A stakeholder requests that a completed backlog item be changed after it was accepted. What should the Product Owner do?
- Reopen the completed item and have the team revise it immediately
- Create a new backlog item for the change and prioritize it appropriately (Correct answer)
- Reject the change since the item was already accepted
- Ask the Scrum Master to negotiate with the stakeholder
Correct answer: Create a new backlog item for the change and prioritize it appropriately
Accepted work is done; new requirements become new backlog items to be prioritized against other work.
Question 3: What is the primary difference between an Epic and a User Story in backlog management?
- Epics are written by developers; user stories are written by the Product Owner
- Epics are large bodies of work that are decomposed into smaller user stories (Correct answer)
- Epics are completed in a single sprint; user stories span multiple sprints
- Epics require formal sign-off; user stories do not
Correct answer: Epics are large bodies of work that are decomposed into smaller user stories
Epics represent large features or goals that must be broken down into deliverable user stories before the team can implement them.
Question 4: Which activity ensures that the product backlog reflects the current understanding of the product and market?
- Sprint retrospective
- Daily Scrum
- Continuous backlog refinement (Correct answer)
- Release planning meeting
Correct answer: Continuous backlog refinement
Continuous refinement keeps the backlog aligned with evolving business needs, stakeholder feedback, and market changes.
Question 5: A Product Owner wants to add a new feature mid-sprint that wasn't in the sprint backlog. What is the correct action?
- Add it to the sprint backlog immediately
- Interrupt the team to incorporate the feature
- Add it to the product backlog and prioritize it for a future sprint (Correct answer)
- Ask the Scrum Master to cancel the sprint
Correct answer: Add it to the product backlog and prioritize it for a future sprint
Mid-sprint additions belong in the product backlog; the sprint backlog is fixed once the sprint begins to protect the team's commitment.
Question 6: When using MoSCoW prioritization for a product backlog, what does the 'S' represent?
- Strategic
- Should have (Correct answer)
- Scalable
- Stakeholder-driven
Correct answer: Should have
MoSCoW stands for Must have, Should have, Could have, and Won't have — 'S' is 'Should have,' items important but not critical.
Question 7: What is the role of acceptance criteria in product backlog items?
- They define the team's velocity for the sprint
- They specify the conditions that must be met for an item to be considered done (Correct answer)
- They document the technical architecture for implementation
- They set the release date for the feature
Correct answer: They specify the conditions that must be met for an item to be considered done
Acceptance criteria are testable conditions that confirm a backlog item meets business and functional requirements when completed.
Agile Business Analysis Product Backlog Management 3
Which of the following BEST describes the concept of a 'ready' product backlog item?