Explanation
One way that Lean-Agile leaders can exemplify the SAFe Core Value of alignment is by participating in backlog visibility, review, and preparation1. This means that leaders are actively involved in understanding and prioritizing the work items that deliver value to the customers and stakeholders. They also provide feedback and guidance to the teams and trains that execute the work. By participating in backlog management, leaders can ensure that the work is aligned with the vision, mission, and strategy of the enterprise or government agency2.
1: The Evolving Role of Managers in Lean-Agile Development - Scaled Agile Framework 2: Core Values - Scaled Agile Framework

Explanation
The result of traditional 'at the end' quality and compliance is that it leads to missed opportunities for iterative compliance assessment1. This means that the quality and compliance activities are deferred until the end of the development cycle, when the solution is already built and ready for testing. This approach increases the risk of finding defects and non-compliances late in the process, which can cause delays, rework, and waste2. It also prevents the teams from getting early feedback and validation from the compliance authorities, which can help them adjust and improve their work incrementally3. By applying the SAFe principle of building incrementally with fast, integrated learning cycles, the teams can integrate quality and compliance into their regular flow of work and deliver solutions that meet the regulatory and industry standards more efficiently and effectively4.
1: Government - Building in Quality and Compliance - Scaled Agile Framework 2: Quality vs. Compliance:
What is the difference and what are the common pitfalls? - Honeywell 3: Achieving Regulatory and Industry Standards Compliance with the Scaled Agile Framework (SAFe) 4: Principle #6 - Visualize and limit WIP, reduce batch sizes, and manage queue lengths - Scaled Agile Framework

Explanation
The true statement about Lean-Agile development and contracting is A. Quality is built-in through collaboration and automation. Lean-Agile development is an iterative and incremental approach to software development that emphasizes flexibility, adaptability, and continuous improvement. Quality is not something that is added at the end of the development cycle, but rather something that is embedded throughout the process. Lean-Agile teams collaborate with customers and stakeholders to define clear and testable acceptance criteria for each work item. They also use automation tools to perform frequent testing, integration, and deployment of the software, ensuring that the solution meets the quality standards and compliance requirements12.
1: Advanced Topic - Agile Contracts - Scaled Agile Framework 2: Government - Building in Quality and Compliance - Scaled Agile Framework

Explanation
According to the Visualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengths article on the Scaled Agile Framework website, batch size optimization happens over time as teams figure out the balance between holding cost and transaction cost. The article states that "To improve the economics of handling smaller batches-and thus increase throughput-teams must focus on reducing the transaction costs of any batch. This is a continuous improvement activity that happens over time as teams figure out the balance between holding cost and transaction cost." Therefore, the correct answer is A, batch size optimization happens over time as teams figure out the balance between holding cost and transaction cost. The other options are not accurate, as they are not the statements that are true about optimizing batch sizes for newly-formed SAFe teams in a program. Batch size is not optimized immediately by looking at transaction and holding costs (B), as it takes time for teams to understand the nature of the work, identify bottlenecks, and find the optimal batch size that minimizes both costs. Batch size is not already optimized if there is continuous flow , as optimization involves finding the right balance between batch size and costs, even within a continuous flow environment. Batch size is not optimized when transaction and holding costs seldom change (D), as holding costs and transaction costs can change over time due to various factors such as team size, workload, and external dependencies.