← All SAFE Flashcard Decks

Continuous Delivery Pipeline and DevOps Flashcards

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

Read the first 6 Continuous Delivery Pipeline and DevOps flashcards as text
  1. What is the purpose of 'Refactoring' in SAFe's continuous delivery context?

    Answer: Improving the internal structure of code without changing its external behavior to reduce technical debt

    Refactoring improves code maintainability, readability, and design without altering behavior — essential for sustaining delivery velocity over time.

  2. What is 'Technical Debt' in SAFe and why is it important to manage?

    Answer: The implied cost of future rework caused by choosing expedient solutions now instead of better approaches

    Technical Debt is the accumulated cost of shortcuts and deferred work — if unmanaged, it slows velocity, increases defects, and makes the system harder to change.

  3. In SAFe, what is the 'Minimum Viable Product (MVP)' used for?

    Answer: A version of a new product with just enough features to test a hypothesis and gather validated learning from real users

    An MVP is the smallest experiment that tests the most critical assumption of a business hypothesis, generating real user data to inform the next build-measure-learn cycle.

  4. What is 'Continuous Deployment' in a SAFe context?

    Answer: The practice of automatically deploying every code change that passes automated tests to production or a production-like environment

    Continuous Deployment automates the pipeline from code commit through testing to production deployment, minimizing human intervention and maximizing delivery speed.

  5. What does 'Flow Metrics' in SAFe include?

    Answer: Flow Velocity, Flow Time, Flow Efficiency, Flow Load, and Flow Distribution — measuring the health of the value stream

    SAFe's Flow Metrics (Velocity, Time, Efficiency, Load, Distribution) measure how well work moves through the value stream, revealing improvement opportunities.

  6. What is the 'DevOps Health Radar' in SAFe used for?

    Answer: Assessing an organization's DevOps maturity across the CALMR dimensions to identify gaps and improvement areas

    The DevOps Health Radar is a self-assessment tool that scores an organization on the five CALMR dimensions, revealing which areas to prioritize for DevOps improvement.