← All CAE Flashcard Decks

Agile Principles & Mindset Flashcards

7 cards from real CAE 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 Principles & Mindset flashcards as text
  1. The Agile Manifesto values 'responding to change' over what?

    Answer: Following a plan

    The fourth Agile Manifesto value explicitly prioritizes responding to change over following a plan.

  2. Which Agile principle emphasizes that business people and developers must work together daily throughout a project?

    Answer: Principle 4

    Agile Principle 4 states that business people and developers must work together daily throughout the project.

  3. An Agile team is under pressure to skip the retrospective. What is the BEST response?

    Answer: Advocate for keeping the retrospective as it drives continuous improvement

    Retrospectives are a core Agile practice enabling continuous improvement, and skipping them undermines the inspect-and-adapt cycle.

  4. What does 'sustainable pace' mean in an Agile context?

    Answer: Teams work at a rate they can maintain indefinitely without burnout

    Agile Principle 8 calls for sponsors, developers, and users to maintain a constant, sustainable pace indefinitely.

  5. A product owner wants to add a large feature mid-sprint without removing anything. How should an Agile team respond?

    Answer: Explain the impact on the sprint goal and negotiate scope or defer to the next sprint

    Agile teams protect the sprint goal while welcoming change through transparent communication and negotiation, not unilateral acceptance or rejection.

  6. Which mindset shift is MOST central to adopting Agile?

    Answer: From output-focused to outcome-focused delivery

    Agile focuses on delivering value and outcomes rather than simply completing tasks or producing outputs.

  7. Which of the following BEST illustrates the Agile principle of 'simplicity — the art of maximizing work not done'?

    Answer: Building only the features customers actually need rather than speculative functionality

    Simplicity in Agile means avoiding unnecessary features or work that doesn't directly deliver customer value.