← All DA Flashcard Decks

Agile Frameworks and Methodologies Flashcards

7 cards from real DA 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 Frameworks and Methodologies flashcards as text
  1. In Disciplined Agile, which framework introduced the concept of 'Inspect and Adapt' as a formal event?

    Answer: Scrum

    Scrum introduced 'Inspect and Adapt' as core empirical feedback loops embedded in its Sprint Retrospective and Sprint Review events.

  2. Which DA process blade is most concerned with how teams choose their way of working?

    Answer: Choose Your WoW

    The 'Choose Your WoW' principle in DA empowers teams to select and tailor their Way of Working based on their context.

  3. Kanban's primary mechanism for managing flow is:

    Answer: Visual WIP limits on a pull system

    Kanban uses explicit Work In Progress (WIP) limits on a pull-based board to manage and optimize flow.

  4. In the DA toolkit, what role does Lean thinking play across all life cycles?

    Answer: It provides the philosophical foundation for reducing waste and optimizing flow

    Lean thinking underpins DA's approach by focusing on eliminating waste, delivering value, and optimizing the whole system.

  5. Which of the following best describes the Exploratory (Lean Startup) life cycle in DA?

    Answer: An iterative approach focused on proving business viability via experiments

    The Exploratory life cycle uses Lean Startup techniques like build-measure-learn cycles to validate business hypotheses before full development.

  6. SAFe's Agile Release Train (ART) typically consists of how many teams?

    Answer: 5-12 teams

    A SAFe ART typically consists of 5-12 Agile teams (50-125 people) who synchronize on a common Program Increment cadence.

  7. In LeSS (Large-Scale Scrum), how many Product Owners exist across all teams?

    Answer: One overall Product Owner for all teams

    LeSS maintains a single Product Owner who owns one Product Backlog shared across all teams to preserve product cohesion.