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

Agile Planning & Estimation Flashcards

7 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 7 Agile Planning & Estimation flashcards as text

  1. In MoSCoW prioritization, the 'S' stands for:

    Answer: Should have

    MoSCoW stands for Must have, Should have, Could have, and Won't have — 'S' represents 'Should have,' items important but not critical for the current release.

  2. T-shirt sizing (XS, S, M, L, XL) is best used during which phase of Agile planning?

    Answer: High-level roadmap and portfolio-level estimation

    T-shirt sizing is a quick, relative estimation technique used at the roadmap or portfolio level when precision is not yet needed or possible.

  3. The Cone of Uncertainty in Agile planning illustrates that:

    Answer: The team's confidence increases as the project progresses and unknowns are resolved

    The Cone of Uncertainty shows that estimation ranges are widest at the start and narrow as the team learns more through actual delivery, reducing unknowns.

  4. Rolling wave planning in Agile refers to the practice of:

    Answer: Planning near-term work in detail while keeping future work at a higher level

    Rolling wave planning acknowledges uncertainty by detailing only near-term work and progressively elaborating future work as more information becomes available.

  5. A sprint burndown chart shows:

    Answer: Remaining work (story points or tasks) plotted against time within a sprint

    A sprint burndown chart tracks remaining work against time, allowing the team to see at a glance whether they are on track to complete sprint commitments.

  6. The INVEST criteria for user stories include which of the following attributes?

    Answer: Independent, Negotiable, Valuable, Estimable, Small, Testable

    INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable — a checklist for evaluating the quality of a user story.

  7. A 'spike' story in Agile planning is used to:

    Answer: Allocate time for research or experimentation to reduce uncertainty before estimation

    A spike is a time-boxed investigation or proof-of-concept that reduces uncertainty, enabling the team to estimate related stories more accurately afterward.