Practice Test Geeks(AAC) Agile Analysis Certification Practice Test
← All AAC Flashcard Decks

AAC Product Vision & Backlog Management Flashcards

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

Read the first 6 AAC Product Vision & Backlog Management flashcards as text

  1. When prioritizing the product backlog, the MoSCoW method categorizes items as:

    Answer: Must have, Should have, Could have, Won't have

    MoSCoW stands for Must have, Should have, Could have, and Won't have — a widely used prioritization framework in agile analysis.

  2. What is a 'Definition of Ready' (DoR) in the context of backlog management?

    Answer: The criteria a backlog item must meet before the team can work on it in a sprint

    The Definition of Ready defines the minimum conditions a backlog item must satisfy (e.g., clear acceptance criteria, estimated) before the team accepts it into a sprint.

  3. In agile analysis, value stream mapping is used to:

    Answer: Visualize and analyze the flow of work to identify waste and bottlenecks

    Value stream mapping visualizes the end-to-end flow of work from request to delivery, helping teams identify waste, delays, and improvement opportunities.

  4. Which backlog prioritization approach ranks items based on business value divided by effort (cost)?

    Answer: Weighted Shortest Job First (WSJF)

    Weighted Shortest Job First (WSJF) prioritizes backlog items by calculating the ratio of Cost of Delay to job duration, favoring high-value, low-effort work.

  5. What is the purpose of a 'product goal' as defined in the Scrum framework?

    Answer: To describe the future state of the product that guides backlog decisions

    The product goal is a long-term objective for the Scrum team that provides context and direction for the product backlog, guiding what is added and prioritized.

  6. When an agile analyst creates an impact map, the four levels of the map are:

    Answer: Why, Who, How, What

    An impact map is structured as Why (goal) → Who (actors) → How (impacts) → What (deliverables), linking business goals directly to product features.