Practice Test Geeks(APM) Agile Product Management Certification Practice Test
← All APM Flashcard Decks

Product Backlog Management and Prioritization Flashcards

7 cards from real APM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Product Backlog Management and Prioritization flashcards as text

  1. A product owner uses dot voting during refinement to prioritize features. What is a key limitation of this technique?

    Answer: It reflects team opinion rather than data-driven customer value

    Dot voting captures team preferences but may not reflect actual customer value, user research, or business impact, leading to popularity-biased prioritization.

  2. What does 'backlog depth' refer to in Agile product management?

    Answer: How many sprints' worth of ready and refined work is available at any time

    Backlog depth measures how many sprints of refined, ready work are queued up, ensuring the team always has actionable items without long planning delays.

  3. In a discovery-driven product environment, how should a product owner treat assumptions in backlog items?

    Answer: Document assumptions explicitly and plan experiments or spikes to validate them early

    Making assumptions explicit and validating them with lightweight experiments reduces risk and prevents teams from building features based on false premises.

  4. Which prioritization technique ranks items using three categories: Must Have, Should Have, Could Have, and Won't Have?

    Answer: MoSCoW

    MoSCoW is a prioritization method that categorizes requirements into Must Have, Should Have, Could Have, and Won't Have to align stakeholders on scope.

  5. A product owner discovers that two top-priority backlog items have a strong technical dependency. What is the BEST response?

    Answer: Identify the dependency, reorder items so the blocker is implemented first, and communicate the dependency

    Dependencies must be made visible and managed by resequencing work so blockers are addressed before the items that depend on them, preserving flow.

  6. What is the role of 'acceptance criteria' in a backlog item?

    Answer: To define the specific conditions that must be met for the item to be considered complete

    Acceptance criteria are the testable conditions that define 'done' for a user story, providing shared understanding between the product owner and development team.

  7. Which approach helps a product owner manage a backlog that spans multiple Agile teams working on the same product?

    Answer: A single product backlog owned by one product owner, with team-level coordination during planning

    In scaled Agile, one product backlog with one product owner ensures alignment; team-level backlogs are derived from it during Sprint or PI Planning.