SAFe-DevOps Sample Questions Answers

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, working in isolation on long-lived code branches can have negative consequences for the Continuous Delivery Pipeline. This includes making the trunk/main branch less stable and more prone to conflicts and errors. The handbook states that "Working in isolation on long-lived code branches can make the trunk/main branch less stable and more prone to conflicts and errors."1 Therefore, it is recommended to use short-lived feature branches and merge them frequently into the trunk/main branch.

According to the SAFe DevOps Practitioner 6.0 study guide1, when prioritizing improvement items, the steps with short Active Time and high %C&A in the future-state map should be the main focus. Active Time is the amount of time a step spends on performing work, while %C&A is the percentage of capacity utilization of a step. The future-state map shows how the Value Stream will look like after implementing improvements, based on customer feedback and business value. The improvement items are ranked by their impact on flow efficiency, customer satisfaction, and business agility. The steps with short Active Time and high %C&A in the future-state map indicate that they are bottlenecks or waste sources that need to be eliminated or reduced as soon as possible. Therefore, they should be prioritized for improvement actions.

The purpose of the blue/green deployment pattern is to deploy between an inactive and active environment. The blue/green deployment pattern is a change management strategy for software releases that reduces the downtime and risk of deploying new versions of software. The blue/green deployment pattern involves having two identical but separate environments: one is the active environment (blue) that serves the user traffic, and the other is the inactive environment (green) that hosts the new version of the software. The deployment process consists of switching the user traffic from the blue environment to the green environment, after verifying that the new version is working properly. The blue environment can then be kept as a backup or updated to become the next green environment. The blue/green deployment pattern has several benefits, such as:

• It allows for fast and reliable rollback, in case of any issues or errors in the new version, by simply switching back to the blue environment.
• It eliminates the need for complex and error-prone migration scripts, as the green environment can be prepared and tested in advance, without affecting the blue environment.
• It enables testing and experimentation of the new version with a subset of users, by directing some user traffic to the green environment, before switching completely.
• It facilitates continuous delivery and deployment, by automating the switching process and reducing the transaction cost and risk of moving changes to production

Blue/green deployment falls outside the scope of the Stabilize activity. The Stabilize activity is part of the Release on Demand aspect of the Continuous Delivery Pipeline, which is responsible for releasing new functionality to end users, either immediately or incrementally, based on business and customer needs. The Stabilize activity ensures that the solution is working well from a functional and nonfunctional perspective, and that it can be operated and supported effectively. The Stabilize activity involves the following practices:

• Continuous security monitoring – Applying automated tools and processes to detect and respond to security threats and vulnerabilities in the production environment, and ensuring compliance with security policies and standards.
• Failover and recovery processes – Establishing and testing backup and restore mechanisms, disaster recovery plans, and business continuity procedures, to ensure the availability and resilience of the solution in case of failures or disruptions.
• Features monitoring – Collecting and analyzing data on the usage, performance, and outcomes of the released features, to measure their value and impact, and to identify any issues or defects that need to be fixed or improved.
• Support and maintenance – Providing ongoing support and maintenance for the solution, such as resolving incidents, handling requests, applying patches, and performing upgrades, to ensure the reliability and quality of the solution.

Blue/green deployment, on the other hand, is a technical practice that belongs to the Continuous Deployment aspect of the Continuous Delivery Pipeline, which is responsible for deploying new functionality into the production environment, where it can be tested and validated. Blue/green deployment is a change management strategy that reduces the downtime and risk of deploying new versions of software. It involves having two identical but separate environments: one is the active environment that serves the user traffic (blue), and the other is the inactive environment that hosts the new version of the software (green). The deployment process consists of switching a small portion of the user traffic from the blue environment to the green environment, after verifying that the new version is working properly. The portion of users who receive the new version are called canaries, as they serve as early indicators of the quality and performance of the new version. If the canary release is successful, the entire user traffic is gradually switched to the green environment, which becomes the new active environment. If the canary release fails, the user traffic is switched back to the blue environment, which remains the active environment. Blue/green deployment has several benefits, such as:

• It allows for fast and reliable rollback, in case of any issues or errors in the new version, by simply switching back to the active environment.
• It eliminates the need for complex and error-prone migration scripts, as the inactive environment can be prepared and tested in advance, without affecting the active environment.
• It enables testing and experimentation of the new version with a subset of users, by directing some user traffic to the inactive environment, before switching completely.
• It facilitates continuous delivery and deployment, by automating the switching process and reducing the transaction cost and risk of moving changes to production

According to the SAFe DevOps Practitioner 6.0 study guide1, feature toggles are useful for decoupling deployment from release. Feature toggles are a technique that allows code to be turned “on” or “off” without needing additional deployment. Feature toggles enable teams to experiment with different features, validate their assumptions, and learn from their failures without affecting the rest of the system. Feature toggles also help teams to reduce the risk of deploying faulty or incomplete code, as well as to optimize the performance and resource consumption of the system. Therefore, feature toggles are useful for decoupling deployment from release, which is an aspect of the Continuous Delivery Pipeline that releases new functionality immediately or incrementally based on business and customer needs2.

According to the SAFe DevOps Practitioner 6.0 study guide1, hypothesis evaluation is important when analyzing data from monitoring systems in the Release on Demand aspect because it helps link objective production data to the hypothesis being tested. Hypothesis evaluation is the process of measuring and comparing the actual outcomes of a hypothesis with the expected outcomes based on customer feedback and business value. Hypothesis evaluation helps DevOps teams to validate or invalidate their hypotheses, learn from their mistakes, and improve their solutions. By linking objective production data to the hypothesis being tested, DevOps teams can see how well their solutions are delivering value to customers and achieving their goals.

Mapping the value stream helps accomplish two actions: to gain insight into organizational efficiency and to understand how the flow of value can be improved. A value stream is the series of steps that an organization uses to implement solutions that provide a continuous flow of value to a customer. Mapping the value stream involves identifying the steps, people, inputs, outputs, tools, and metrics involved in delivering value from concept to cash. By mapping the value stream, the organization can gain insight into the current state of the delivery process, such as the lead time, cycle time, throughput, quality, and waste. This insight can help the organization identify bottlenecks, dependencies, handoffs, delays, and inefficiencies that affect the flow of value. Mapping the value stream also helps the organization understand how the flow of value can be improved by applying the principles and practices of DevOps, such as culture, automation, lean flow, measurement, and recovery. By improving the flow of value, the organization can increase customer satisfaction, reduce costs, accelerate time-to-market, and enhance business agility

When preparing a DevOps backlog, prioritizing features using WSJF includes two factors: cost of delay and duration/job size. WSJF stands for Weighted Shortest Job First, which is a prioritization model used to sequence work for maximum economic benefit. WSJF is estimated as the relative cost of delay divided by the relative job duration. Cost of delay is the money lost by delaying or not doing a job for a specific time. It is a measure of the economic value of a job over time. Job duration is the time it takes to complete a job. Jobs that can deliver the most value in the shortest duration provide the best economic return. WSJF also considers other factors that contribute to the cost of delay, such as user and business value, time criticality, and risk reduction and/or opportunity enablement

After conducting current-state mapping in the context of Value Stream Mapping, a team should be able to identify and describe the biggest bottlenecks in the delivery pipeline. Current-state mapping is a process of visualizing the entire flow of a product or service from start to finish, highlighting each step and identifying where delays or inefficiencies occur. By understanding where these bottlenecks are, teams can then work on strategies to improve the overall flow, reduce lead times, and enhance efficiency. This step is crucial for identifying areas for improvement and setting the stage for future actions to optimize the Value Stream.

The desired frequency of deployment in SAFe is continuous, meaning that new functionality can be deployed to production as soon as it is ready, without waiting for fixed release dates or schedules. Continuous deployment is an aspect of the CDP that automates the migration of new functionality from a staging environment to production, where it is made available for release. Continuous deployment enables the ability to release value at any time, in a sustainable way

According to the SAFe DevOps Practitioner 6.0 study guide1, one of the benefits of DevOps is better alignment between strategy and execution. DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps helps break down organizational silos and develop a Continuous Delivery Pipeline (CDP) — a high-performance innovation engine capable of delivering market-leading solutions at the speed of business. By aligning strategy and execution, DevOps enables teams to deliver value to customers faster and more reliably, as well as to adapt to changing market conditions and customer needs. Therefore, better alignment between strategy and execution is one of the benefits of DevOps.

Refactoring is the activity of improving the internal structure or operation of a code or component without changing its external behavior. The goal of software development is the continuous delivery of business value to users and stakeholders. Constantly changing technology and evolving business objectives make maintaining and continuously increasing business value difficult. Refactoring enables an emergent design, ensuring the system continues to meet future business needs. Refactors are a particular type of Enabler story in SAFe, and, like any other Story, they must be estimable, verifiable, and valuable, as well as accepted by the Product Owner. SAFe emphasizes the importance of keeping all work visible, including refactoring. Like user value work, refactoring must be planned for, estimated, and prioritized. Therefore, developers should create and estimate refactoring Stories in the Team Backlog, and work on them according to their WSJF1

One of the measurable benefits of adopting DevOps practices and principles is that it results in faster lead time and more frequent deployments. Lead time is the time it takes from the moment a change is requested until it is delivered to the customer. Frequent deployments are the number of times a change is deployed to production. Both of these metrics indicate the speed and efficiency of the DevOps process, as well as the ability to respond to customer needs and feedback. According to the State of DevOps Report 2020, high-performing DevOps teams have 208 times faster lead times and 106 times more frequent deployments than low-performing teams

The recommended way to prioritize improvement items for the DevOps transformation is to use Weighted Shortest Job First (WSJF). WSJF is a prioritization model that considers the cost of delay, job size, and economic value of each improvement item. It helps to identify the most urgent and valuable items that can be delivered in the shortest amount of time

Two benefits of DevOps are fewer defects and less time spent fixing security issues. DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps helps break down organizational silos and develop a Continuous Delivery Pipeline — a high-performance innovation engine capable of delivering market-leading solutions at the speed of business. DevOps has many benefits for the enterprise, such as:

• Fewer defects – DevOps improves the quality and consistency of the solution by enforcing frequent testing and validation throughout the solution lifecycle. DevOps applies various testing techniques and tools, such as unit testing, integration testing, acceptance testing, performance testing, and security testing, to verify that the solution meets the functional and nonfunctional requirements and standards. DevOps also enables early detection and resolution of defects, by implementing fast and frequent feedback loops within and across the value stream. DevOps reduces the cost and risk of defects, by shifting quality left and building quality in, rather than inspecting quality out.
• Less time spent fixing security issues – DevOps enhances the security and compliance of the solution by integrating security practices into the value stream. DevOps applies the DevSecOps approach, which emphasizes the importance of proper information security practices in the pursuit of continuous delivery. DevSecOps involves applying automated tools and processes to detect and respond to security threats and vulnerabilities in the development and production environments, and ensuring compliance with security policies and standards. DevSecOps also involves collaborating with security teams and stakeholders, to foster a culture of shared responsibility and awareness for security. DevSecOps reduces the time and effort spent on fixing security issues, by shifting security left and building security in, rather than bolting security on8

Two areas that should be monitored in the Release on Demand aspect to support DevOps and Continuous Delivery are the build status and the deployment cycle time. The build status is the measure of whether the code and components can be successfully compiled, linked, packaged, and verified into deployable binaries. The build status indicates the quality and consistency of the code and the readiness for deployment. Monitoring the build status helps to support the Release on Demand aspect in SAFe by providing valuable information for the following purposes:

• To identify and fix any errors or defects that may prevent the code from being deployed or released
• To ensure that the code meets the quality standards and security checks, such as static code analysis, code coverage, and code review
• To verify that the code and components are integrated and merged correctly into the trunk
• To track the progress and status of the features and capabilities that are being developed and delivered

The deployment cycle time is the measure of how long it takes to deploy the code and components from the source control system to the production environment. The deployment cycle time indicates the efficiency and reliability of the deployment process and the speed of delivery. Monitoring the deployment cycle time helps to support the Release on Demand aspect in SAFe by providing valuable information for the following purposes:

• To optimize the deployment process and reduce the lead time and variability
• To automate the deployment process and eliminate manual steps and errors
• To align the deployment process with the market demand and release strategy
• To evaluate the impact and value of the deployed features and capabilities 7

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the Release activity is triggered by a business decision to go live. This means that the Solution is ready to be delivered to end users and customers, based on the validation and testing done in the previous activities. The handbook states that "The Release activity is triggered by a business decision to go live."1 Therefore, this activity involves releasing value to customers on demand, while also measuring and learning from the feedback.

The statement that is true about DevOps is that it enables low-risk releases and fast recovery with fast fix-forward. DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps aims to deliver value to customers whenever there is a business need, by applying the principles of continuous delivery, continuous integration, continuous deployment, and release on demand. DevOps also embraces a culture of learning and experimentation, where failures are opportunities for improvement and feedback. DevOps enables low-risk releases by breaking down large and complex changes into smaller and more frequent batches, which are easier to test, deploy, and rollback if needed. DevOps also enables fast recovery by implementing practices such as monitoring, alerting, incident response, and disaster recovery, which help to detect and resolve issues quickly, minimize the impact of failures, and restore normal operations as soon as possible. DevOps also supports the fast fix-forward approach, which means fixing errors in production by deploying new code, rather than rolling back to a previous state. This approach reduces the risk of introducing new errors, preserves the value of the new functionality, and accelerates the learning cycle

After the team maps the steps of the current state value stream during value stream mapping, the next two steps are to measure the performance at each step and calculate the activity ratio. Measuring the performance at each step involves collecting data on cycle time, lead time, process time, wait time, defect rate, and other relevant metrics. This helps to identify the sources of waste, delays, and inefficiencies in the value stream. Calculating the activity ratio involves dividing the total process time by the total lead time and multiplying by 100. This gives the percentage of time that is spent on value-adding activities versus non-value-adding activities. The activity ratio helps to quantify the flow and identify opportunities for improvement

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, specific improvements to the Continuous Delivery Pipeline are identified in Future-state Value Stream Mapping. This activity involves envisioning and designing the ideal state of the value stream, based on the current state and the desired outcomes. The handbook states that "Future-state Value Stream Mapping is a way of defining how you want your value stream to look like in the future."1 Therefore, Future-state Value Stream Mapping helps teams identify and prioritize the areas that need improvement in their Continuous Delivery Pipeline.

The people responsible for the next step should be consulted first when calculating the % Complete and Accurate (%C&A) metric. The %C&A metric is a measure of the quality of the work output from a process step. It indicates the percentage of time that the downstream customers receive work that is acceptable as is, without any rework or errors. To calculate the %C&A metric, the people responsible for the next step need to inspect the work output from the previous step and determine whether it meets the quality standards and expectations. They also need to provide feedback to the previous step on the defects or issues they find and how they affect the value stream. By consulting the people responsible for the next step, the %C&A metric can reflect the actual customer satisfaction and the potential waste in the process1

The output of the Release activity is a Feature made available to end users. The Release activity is the final aspect of the Continuous Delivery Pipeline (CDP) in SAFe DevOps, which enables the delivery of value to the end user as fast as possible, based on market demand. The Release activity involves the practices needed to deliver the solution to end users, all at once or incrementally. The Release activity is a business decision that requires careful consideration of the customer needs, market rhythms, and economic outcomes. The Release activity is decoupled from the Continuous Deployment activity, which automates the migration of new functionality from a staging environment to production, where it is made available for release

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, value flows through Continuous Integration in the Continuous Delivery Pipeline. This aspect involves merging code changes from multiple developers into a shared repository and running automated tests to ensure quality and functionality. The handbook states that "Continuous Integration is the process of merging code changes from multiple developers into a shared repository and running automated tests to ensure quality and functionality."1 Therefore, Continuous Integration enables teams to deliver value faster and more reliably by reducing integration errors and conflicts.

According to the SAFe DevOps Practitioner 6.0 study guide1, one of the organizational anti-patterns that DevOps helps to address is teams that are isolated and working within functional areas (e.g., business, operations, and technology). This anti-pattern creates silos, conflicts, and inefficiencies that hinder the collaboration and integration needed for continuous delivery. For example, some teams may prioritize speed over quality, while others may prioritize security over innovation. Some teams may resist change and adopt outdated practices, while others may embrace new technologies and methodologies. These differences can lead to misalignment, duplication, and waste of resources that slow down the delivery pipeline and reduce the value to customers. Therefore, DevOps helps to break down the functional silos and enable cross-functional teams that work together to deliver value to customers faster and more reliably.

The main goal of a SAFe DevOps transformation is to align people across the Value Stream to deliver value continuously. A Value Stream is the primary construct for understanding, organizing, and delivering value to the customer. A SAFe DevOps transformation involves applying the CALMR approach (Culture, Automation, Lean flow, Measurement, and Recovery) to the four aspects of the CDP (Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand). By doing so, the organization can achieve the following benefits: faster time-to-market, higher quality, lower costs, better customer satisfaction, and improved employee engagement5