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

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.

According to the SAFe DevOps Practitioner 6.0 study guide1, the Release activity is the final step in the Continuous Delivery Pipeline that deploys the Solution to production. Production is where the Solution is available for end users to operate and consume. The Release activity involves verifying that the Solution meets the quality and security requirements, monitoring its performance and health, and responding to any issues or incidents that may arise. The Release activity also enables continuous improvement by measuring the business value of the Solution and collecting feedback from customers and stakeholders.

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

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