RTE DevOps and Release on Demand 1 — Questions and Answers
Question 1: What is the DevOps dimension of SAFe focused on?
- Managing hardware procurement
- Creating a continuous delivery pipeline that allows the ART to release value on demand (Correct answer)
- Tracking developer productivity metrics
- Replacing Agile ceremonies with automated tooling
Correct answer: Creating a continuous delivery pipeline that allows the ART to release value on demand
The DevOps dimension of SAFe focuses on building a Continuous Delivery Pipeline (CDP) that enables the ART to release high-quality value to customers on demand.
Question 2: What are the four aspects of SAFe's Continuous Delivery Pipeline?
- Plan, Build, Test, Deploy
- Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand (Correct answer)
- Discovery, Development, Testing, Operations
- Backlog, Sprint, Review, Retrospective
Correct answer: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand
SAFe's CDP consists of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand, each representing a stage of value delivery.
Question 3: What does 'Release on Demand' mean in SAFe?
- Releasing software immediately after every commit
- Releasing functionality to customers when and how the business needs it, decoupled from the development cycle (Correct answer)
- Allowing customers to request specific features at any time
- Scheduling all releases at the end of each PI
Correct answer: Releasing functionality to customers when and how the business needs it, decoupled from the development cycle
Release on Demand means the ART can release features to customers at any time, decoupled from the development cadence, enabling the business to control when value reaches end users.
Question 4: What is a Feature Toggle (Feature Flag) and why is it relevant to the RTE?
- A project management switch to pause feature development
- A technique to deploy code to production while hiding it from users until the business is ready to release (Correct answer)
- A bug tracking label used by QA teams
- A permission setting in the development environment
Correct answer: A technique to deploy code to production while hiding it from users until the business is ready to release
Feature toggles allow teams to deploy code to production in a hidden state, giving the business control over when features are activated, supporting release on demand.
Question 5: What role does the RTE play in promoting DevOps practices within the ART?
- Writing DevOps scripts for the teams
- Coaching teams to adopt CI/CD practices, removing organizational impediments to pipeline adoption, and fostering a DevOps mindset (Correct answer)
- Managing the cloud infrastructure directly
- Approving all DevOps tool purchases
Correct answer: Coaching teams to adopt CI/CD practices, removing organizational impediments to pipeline adoption, and fostering a DevOps mindset
The RTE promotes DevOps by coaching teams on CI/CD adoption, removing impediments like organizational silos, and encouraging a culture of shared responsibility for quality and delivery.
Question 6: What is 'built-in quality' in SAFe and how does it relate to DevOps?
- A certification process for deployed software
- The practice of applying quality at every step of the development process rather than inspecting it in at the end (Correct answer)
- An automated testing tool integrated into the pipeline
- A documentation requirement for regulated industries
Correct answer: The practice of applying quality at every step of the development process rather than inspecting it in at the end
Built-in quality means embedding quality practices — such as TDD, peer review, and automated testing — throughout development so defects are prevented rather than detected late.
RTE DevOps and Release on Demand 1
What is the DevOps dimension of SAFe focused on?