Task 1 Refine Product Backlog PMI-ACP Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   A product owner is prioritizing backlog items and wants to classify features based on how they affect customer satisfaction. Which prioritization technique is most appropriate for this purpose?

   • AMoSCoW method
   • BRelative weighting
   • CPlanning Poker
   • DKano model
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   A team is estimating the relative size of backlog items. They want to use a technique that involves the entire team and uses a deck of cards with numbers like 1, 2, 3, 5, 8, 13. Which technique are they using?

   • APlanning Poker
   • BAffinity estimation
   • CT-shirt sizing
   • DMoSCoW method
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   During backlog refinement, the team is reviewing a large user story that describes a new reporting dashboard. The story is too large to fit into a single iteration, and the team is unsure about the exact requirements. What should the team do to make the story ready for development?

   • ABreak the story down into smaller stories that each deliver a specific reporting capability.
   • BMove the story to the top of the backlog to ensure it is addressed first.
   • CEstimate the story using affinity estimation.
   • DPrioritize the story using relative weighting.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A product owner is prioritizing the backlog with a group of stakeholders. The stakeholders have different opinions about which features are most valuable. The product owner wants to use a technique that quantifies the value and cost of each feature to make an objective decision. Which technique should the product owner use?

   • AMoSCoW
   • BRelative weighting
   • CKano model
   • DPlanning Poker
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   During backlog refinement, the team is reviewing a large epic that describes a complete overhaul of the user profile system. The epic is too large to fit into a single iteration, and the team is struggling to understand the scope. What should the team do to make the epic ready for development?

   • APrioritize the epic using MoSCoW to determine its importance.
   • BEstimate the epic using T-shirt sizing to get a relative size.
   • CDecompose the epic into smaller user stories that each deliver value and can be completed within one iteration.
   • DMove the epic to the top of the backlog so the team can start working on it immediately.
   Reveal Solution Discussion Select an answer first