Scrumは2024年最新のSAFe-DevOpsテスト解説（更新されたのは100問があります)
SAFe-DevOps試験問題集を提供していますScrum問題
質問 # 56
The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to which four stakeholder concerns?
- A. Alignment, quality, time-to-market, business value
- B. Productivity, efficiency, speed-to-market, competitive advantage
- C. Exploration, integration, development, reflection
- D. Portfolio, Solution, ART, team
正解：A
解説：
Explanation
The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to four stakeholder concerns: alignment, quality, time-to-market, and business value. The DevOps Health Radar is a tool that helps Agile Release Trains (ARTs) and Solution Trains assess their ability to Release on Demand, which is the process of delivering value to customers whenever there is a business need. The DevOps Health Radar consists of four dimensions that correspond to the four aspects of the Continuous Delivery Pipeline: Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. Each dimension has four sub-dimensions that reflect the key practices and capabilities that enable the flow of value.
The DevOps Health Radar helps the ARTs and Solution Trains to measure their maturity in each sub-dimension, using a scale of Sit, Crawl, Walk, Run, or Fly. The DevOps Health Radar also helps the ARTs and Solution Trains to identify the gaps and improvement opportunities in their DevOps practices, and to prioritize the next steps toward achieving higher levels of maturity. The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to four stakeholder concerns, as shown in Figure 1:
Alignment - Alignment is the concern of ensuring that the solution is aligned with the customer needs, market opportunities, and strategic goals of the enterprise. Alignment is achieved by applying the CE aspect, which involves exploring the market and customer problems, defining a vision, roadmap, and set of features for the solution, and validating the assumptions and hypotheses with customer feedback and data.
Quality - Quality is the concern of ensuring that the solution meets the functional and nonfunctional requirements and standards, and that it does not introduce any defects or vulnerabilities. Quality is achieved by applying the CI aspect, which involves developing, testing, integrating, and validating new functionality in preparation for deployment and release.
Time-to-market - Time-to-market is the concern of ensuring that the solution can be delivered and deployed to the production environment as fast and as frequently as possible, without compromising quality or security. Time-to-market is achieved by applying the CD aspect, which involves automating and streamlining the deployment process, and ensuring the stability and reliability of the production environment.
Business value - Business value is the concern of ensuring that the solution delivers the expected outcomes and benefits to the customer and the enterprise, and that it can be adapted and improved based on the changing needs and feedback. Business value is achieved by applying the Release on Demand aspect, which involves releasing new functionality to the customer incrementally or immediately, based on the market demand, and measuring and learning from the results12
1: https://scaledagileframework.com/blog/assess-your-devops-health-with-the-safe-devops-radar/ 2:
https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps
質問 # 57
What is true about the Critical Flow Properties portion of the DevOps Transformation Canvas?
- A. It captures the people who need to improve the flow properties
- B. It captures the flow properties that are most in need of improvement
- C. It captures the work-in-process (WIP) limits that should be applied to the Value Stream
- D. It captures the lowest priority improvement items
正解：B
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, the Critical Flow Properties portion of the DevOps Transformation Canvas captures the flow properties that are most in need of improvement. Flow properties are the characteristics of a value stream that affect how well it delivers value to customers. The Critical Flow Properties portion identifies the flow properties that have the most impact on customer satisfaction and business outcomes, and prioritizes improvement actions accordingly. The Critical Flow Properties portion is based on data from monitoring systems, customer feedback, and business value analysis.
Therefore, it captures the flow properties that are most in need of improvement for each value stream.
質問 # 58
Where do features go after Continuous Exploration?
- A. Into Continuous Development, where they are implemented in small batches
- B. Into Continuous Integration, where they are deployed with feature toggles
- C. Into the Portfolio Backlog, where they are then prioritized
- D. Into Continuous Integration, where they are then split into Stories
正解：D
解説：
Explanation
In the Scaled Agile Framework (SAFe), after features are defined and designed during Continuous Exploration, they move into Continuous Integration. Here, they are further broken down into smaller, implementable parts known as user stories. These stories are then developed, tested, and integrated into the existing codebase. This process ensures that new features are developed in a systematic and efficient manner, with regular integration and testing to maintain quality and readiness for release.
質問 # 59
What is one of the top advantages of mapping the current state of the delivery pipeline?
- A. To identify some of the processes within the delivery pipeline
- B. To help identify and make short-term fixes
- C. To achieve a collective understanding and consensus around problems
- D. To help with incremental software delivery
正解：C
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, one of the top advantages of mapping the current state of the delivery pipeline is to achieve a collective understanding and consensus around problems.
Mapping the current state of the delivery pipeline is a technique that helps teams visualize and analyze their current processes, practices, and performance. Mapping the current state of the delivery pipeline enables teams to identify pain points, inefficiencies, and opportunities for improvement. Mapping the current state of the delivery pipeline also fosters collaboration, communication, and alignment among team members and stakeholders. By mapping the current state of the delivery pipeline, teams can gain a shared vision of their current situation, challenges, and goals. This can help them to reach a collective understanding and consensus around problems that need to be solved or opportunities that need to be pursued. Therefore, mapping the current state of the delivery pipeline is an advantage that can improve team cohesion and decision making.
質問 # 60
What are two aspects of the Continuous Delivery Pipeline, in addition to Continuous Integration? (Choose two.) Choose the correct option from below list
- A. Continuous Deployment
- B. Continuous Improvement
- C. Continuous Testing
- D. Continuous Exploration
- E. Continuous Release
正解：A、D
解説：
Explanation
In addition to Continuous Integration, two other aspects of the CDP are Continuous Deployment and Continuous Exploration. Continuous Deployment 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. Continuous Exploration focuses on creating alignment on what needs to be built, using design thinking and hypothesis-driven development. Continuous Exploration enables the discovery of the most valuable solutions for the customers and the enterprise
質問 # 61
What is one benefit of DevOps?
- A. Tightly coupled architecture
- B. Increased batch size
- C. Better alignment between strategy and execution
- D. Fewer defects
正解：C
解説：
Explanation
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.
質問 # 62
What work is performed in the Build activity of the Continuous Delivery Pipeline?
- A. Code review
- B. Compile
- C. Code
- D. Automated acceptance testing
正解：B
解説：
Explanation
The correct answer is B. Compile. The Build activity of the Continuous Delivery Pipeline is responsible for creating deployable binaries and merging development branches into the trunk. The Build activity includes the following practices:
Compile - Compile is the process of transforming the source code into executable code that can run on a specific platform or environment. Compile involves checking the syntax, semantics, and dependencies of the code, and resolving any errors or conflicts. Compile also involves linking the code with other libraries or components that are required for the functionality of the solution.
Package - Package is the process of bundling the compiled code and other resources into a format that can be easily deployed to the target environment. Package involves creating archives, containers, or installers that contain the necessary files and metadata for the deployment process. Package also involves applying versioning and configuration information to the packages, to ensure traceability and consistency.
Verify - Verify is the process of ensuring that the code and packages meet the quality standards and security checks, and that they are ready for deployment and release. Verify involves applying automated tools and processes, such as static code analysis, code coverage, code review, and code quality metrics, to detect and resolve any issues or vulnerabilities in the code and packages. Verify also involves ensuring compliance with the coding standards and guidelines, and documenting the results and feedback of the verification process12
質問 # 63
When preparing a DevOps backlog, prioritizing features using WSJF includes which two factors? (Choose two.) Choose the correct option from below list
- A. Cost of delay
- B. Business value
- C. Team velocity
- D. Total count of items on the Program Backlog
- E. Duration/job size
正解：A、E
解説：
Explanation
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
質問 # 64
Which two security skills are part of the Continuous Integration aspect? (Choose two.)
- A. Application security
- B. Security board review
- C. Penetration testing
- D. Network security practices
- E. SOX compliance analysis
正解：A、C
解説：
Explanation
Two security skills that are part of the Continuous Integration aspect are application security and penetration testing. Application security is the practice of protecting the software applications from malicious attacks, unauthorized access, data breaches, and other threats. It involves applying security principles and techniques throughout the software development lifecycle, such as secure coding, code analysis, code review, security testing, and security monitoring. Application security helps to ensure that the software meets the security requirements and standards, and that it does not introduce any vulnerabilities or risks to the system or the users910 Penetration testing is the practice of simulating real-world attacks on the software applications to identify and exploit any security weaknesses or flaws. It involves using various tools and methods to probe, scan, attack, and bypass the security defenses of the software, such as firewalls, encryption, authentication, and authorization. Penetration testing helps to evaluate the security posture and resilience of the software, and to provide recommendations for improvement or remediation. Penetration testing is usually performed by external or independent experts, who have the permission and authorization to conduct the tests
質問 # 65
What triggers the Release activity?
- A. Successful deployment to production
- B. Successful user acceptance tests
- C. Business decision to go live
- D. Change validated in staging environment
正解：C
解説：
Explanation
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.
質問 # 66
Which practice prevents configuration drift between production and non-production environments?
- A. Self-service deployment
- B. Deployment automation
- C. Immutable infrastructure
- D. Session replay
正解：C
解説：
Explanation
One practice that prevents configuration drift between production and non-production environments is immutable infrastructure. Immutable infrastructure is a management approach for infrastructure resources where changes are made by deploying new versions of resources instead of modifying existing ones. In this approach, the infrastructure is treated as an immutable asset that is built, deployed, and disposed of, rather than modified in place. For example, instead of modifying an existing virtual machine (VM), a new VM with updated configurations and software is deployed, and the old VM is disposed of. This approach eliminates the possibility of configuration drift and reduces the risk of introducing unintended changes to the infrastructure. Immutable infrastructure also simplifies the management of infrastructure resources, increases the reliability and security of the infrastructure, and facilitates rapid and consistent deployment
質問 # 67
What is the primary benefit of value stream mapping?
- A. It identifies how to build Agile Release Trains
- B. It creates the hypothesis of which Solution to build
- C. It provides insight into organizational efficiency and value flow
- D. It fosters collaboration among development and operations managers
正解：C
解説：
Explanation
The primary benefit of value stream mapping is that it provides insight into organizational efficiency and value flow. Value stream mapping is a lean technique to analyze, design, and manage the flow of materials and information required to bring a product or service to a customer. It uses a system of standard symbols to depict various work streams and information flows, and to identify value-adding and non-value-adding activities.
Value stream mapping helps the organization to 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. Value stream mapping 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
質問 # 68
What is the main goal of a SAFe DevOps transformation?
Choose the correct option from below list
- A. To create a strong DevOps team with leadership support
- B. To implement an advanced tool chain to automate the entire Continuous Delivery Pipeline
- C. To align people across the Value Stream to deliver value continuously
- D. To create immutable infrastructure to avoid changes to the production environment
正解：C
解説：
Explanation
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
質問 # 69
Who is responsible for ensuring quality is built into the code in SAFe?
- A. Agile Teams
- B. Product Owners
- C. Testers - xx
- D. Developers
正解：A
解説：
Explanation
Agile Teams are responsible for ensuring quality is built into the code in SAFe. SAFe is a framework for scaling agile practices across the enterprise, based on the principles of Lean, Agile, and DevOps. SAFe organizes the enterprise into Agile Release Trains (ARTs), which are teams of Agile Teams that deliver value in a regular cadence. Agile Teams are the fundamental building blocks of SAFe, and they are cross-functional, self-organizing, and self-managing teams that deliver value in short iterations. Agile Teams are responsible for ensuring quality is built into the code in SAFe, by applying the following practices:
Test-first - Test-first is a practice that involves writing tests before writing code, to ensure that the code meets the requirements and standards, and does not introduce any defects or vulnerabilities. Test-first helps to improve the design and maintainability of the code, and to accelerate the feedback and validation process. Test-first can be implemented using various techniques, such as Test-Driven Development (TDD), Behavior-Driven Development (BDD), or Acceptance Test-Driven Development (ATDD).
Built-in quality - Built-in quality is a practice that involves applying quality standards and checks throughout the solution lifecycle, rather than inspecting quality after the fact. Built-in quality helps to prevent defects from escaping to downstream stages or customers, and to reduce the cost and risk of rework and waste. Built-in quality can be achieved using various methods, such as code quality and security analysis, code review, pair programming, refactoring, and continuous testing.
Continuous testing - Continuous testing is a practice that involves automating and executing tests at every stage of the Continuous Delivery Pipeline, to verify that the solution meets the functional and nonfunctional requirements and standards, and to detect and resolve any issues or defects as early as possible. Continuous testing helps to ensure the reliability and performance of the solution, and to support the delivery and deployment of value to the customer. Continuous testing can be performed using various tools and frameworks, such as unit testing, integration testing, system testing, acceptance testing, performance testing, and security testing
質問 # 70
What is an output of the Release activity?
Choose the correct option from below list
- A. A Feature made available to end users
- B. A Feature migrated to the cloud
- C. A Feature deployed to production
- D. A Feature made available to internal users
正解：A
解説：
Explanation
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
質問 # 71
Feature toggles are useful for which activity?
- A. To enable continuous testing
- B. To decouple deployment from release
- C. To enable continuous code integration
- D. To accelerate the deployment process
正解：B
解説：
Explanation
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.
質問 # 72
What are two parts of the Continuous Delivery Pipeline? (Choose two.)
Choose the correct option from below list
- A. Continuous Delivery
- B. Continuous Security
- C. Continuous Exploration
- D. Continuous Integration
- E. Continuous Experimentation
正解：C、D
解説：
Explanation
The Continuous Delivery Pipeline (CDP) is a key element of the Agile Product Delivery competency in SAFe.
It represents the workflows, activities, and automation needed to guide new functionality from ideation to an on-demand release of value. The CDP consists of four aspects: Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. CE focuses on creating alignment on what needs to be built, using design thinking and hypothesis-driven development. CI focuses on building quality into the solution, using practices such as test automation, code analysis, and continuous feedback
質問 # 73
What does the %C&A metric measure in the Continuous Delivery Pipeline?
- A. The percent complete and average times of each pipeline activity
- B. The percent of time downstream customers receive work that is usable as-is
- C. The percent of change averages of each pipeline activity
- D. The percent concurrent and accurate process times of each pipeline activity
正解：B
解説：
Explanation
The %C&A metric measures the percent of time downstream customers receive work that is usable as-is in the Continuous Delivery Pipeline. 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 measuring the %C&A metric, the enterprise 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 enterprise identify bottlenecks, dependencies, handoffs, delays, and inefficiencies that affect the flow of value. The %C&A metric can also help the enterprise 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 %C&A metric, the enterprise can increase customer satisfaction, reduce costs, accelerate time-to-market, and enhance business agility
質問 # 74
What should be measured in a CALMR approach to DevOps?
- A. Deployment frequency
- B. Flow, quality, and value
- C. Everything
- D. Mean time to restore
正解：B
解説：
Explanation
The correct answer is D. Flow, quality, and value should be measured in a CALMR approach to DevOps. The CALMR approach to DevOps is a mindset that guides the ARTs toward achieving continuous value delivery by enhancing culture, automation, lean flow, measurement, and recovery. Measurement is one of the key elements of the CALMR approach, as it provides data and feedback to monitor and improve the performance and outcomes of the solution delivery process. Measurement involves collecting and analyzing metrics that reflect the flow, quality, and value of the solution, such as:
Flow metrics - Flow metrics measure the efficiency and reliability of the delivery process, such as lead time, cycle time, throughput, work in progress, and flow efficiency. Flow metrics help to identify and eliminate waste and bottlenecks in the value stream, and to optimize the flow of value to the customer.
Quality metrics - Quality metrics measure the functionality and stability of the solution, such as defect rate, defect density, defect leakage, mean time to detect, mean time to resolve, and test coverage.
Quality metrics help to ensure that the solution meets the functional and nonfunctional requirements and standards, and to detect and resolve any issues or defects as early as possible.
Value metrics - Value metrics measure the outcomes and benefits of the solution, such as customer satisfaction, retention, engagement, revenue, and net promoter score. Value metrics help to evaluate the validity of the hypotheses and assumptions about the customer value proposition, and to guide the decision making and prioritization of the features12
質問 # 75
What can impede the progress of a DevOps transformation the most?
- A. When various groups in the organization have different directions and goals
- B. When there is no DevOps team
- C. Lack of funding for CI/CD pipeline tools
- D. When teams use frequent retrospectives
正解：A
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, one of the main challenges of a DevOps transformation is when various groups in the organization have different directions and goals. This can create silos, conflicts, and inefficiencies that hinder the collaboration and integration needed for continuous delivery.
For example, some groups may prioritize speed over quality, while others may prioritize security over innovation. Some groups 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, having a common vision, culture, and set of technical practices that support the SAFe CALMR approach to DevOps is essential for overcoming this challenge.
質問 # 76
Scanning application code for security vulnerabilities is an important step in which aspect of the Continuous Delivery Pipeline?
- A. Continuous Exploration
- B. Continuous Deployment
- C. Continuous Integration
- D. Release on Demand
正解：C
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, scanning application code for security vulnerabilities is an important step in the Continuous Integration aspect of the Continuous Delivery Pipeline.
Continuous Integration is the process of developing, testing, integrating, and validating new functionality in preparation for deployment and release. Continuous Integration helps teams to improve quality, reduce risk, and establish a fast, reliable, and sustainable development pace. Scanning application code for security vulnerabilities is one of the ways to ensure that the code meets the quality standards and requirements, and that it does not contain any errors, bugs, or vulnerabilities that could compromise the security or functionality of the Solution. Scanning application code for security vulnerabilities can be performed by using tools such as GitHub Advanced Security for Azure DevOps2, which uses CodeQL to identify vulnerabilities in various languages and frameworks. Therefore, scanning application code for security vulnerabilities is an important step in the Continuous Integration aspect of the Continuous Delivery Pipeline.
質問 # 77
In which activity are specific improvements to the Continuous Delivery Pipeline identified?
- A. Value Stream identification
- B. Future-state Value Stream Mapping
- C. Impact mapping
- D. Problem-Solving Workshop
正解：B
解説：
Explanation
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.
質問 # 78
Which two technical practices focus on Built-in Quality? (Choose two.)
Choose the correct option from below list
- A. Test-driven development
- B. Canary releases
- C. Feature toggles
- D. Environment configuration
- E. Pair work
正解：A、E
解説：
Explanation
Two of the technical practices that focus on Built-in Quality are pair work and test-driven development. Pair work is a collaborative technique where two developers work together on the same code, one writing the code and the other reviewing it. Pair work improves the quality of the code by reducing defects, increasing knowledge sharing, and enhancing creativity and problem-solving. Test-driven development (TDD) is a practice where developers write automated tests before writing the code, and then refactor the code until it passes the tests. TDD ensures that the code meets the requirements and specifications, as well as improves the design, readability, and maintainability of the code
質問 # 79
Mapping the value stream helps accomplish which two actions? (Choose two.)
- A. To add or remove user segments based on business decisions
- B. To serve as a blueprint for development
- C. To prioritize the Program Backlog
- D. To understand how the flow of value can be improved
- E. To gain insight into organizational efficiency
正解：D、E
解説：
Explanation
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
質問 # 80
......
SAFe-DevOps認定ガイドPDFは100%カバー率でリアル試験問題：https://jp.fast2test.com/SAFe-DevOps-premium-file.html