According to theVisualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengthsarticle 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.

According to theSystem Demoarticle on the Scaled Agile Framework website, system demos provide objective evidence of built-in quality and compliance. The article states that ''The System Demo is a significant event that provides an integrated view of new Features for the most recent Iteration delivered by all the teams in the Agile Release Train (ART). Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI). The system demo is part of the inspect and adapt cycle and provides ARTs with the opportunity to assess their current state, adjust, and improve. The system demo also provides feedback on functional and nonfunctional requirements, such as compliance, performance, security, and usability.'' Therefore, the correct answer is C, system demos. The other options are not accurate, as they are not the events that provide objective evidence of built-in quality and compliance. PI planning (A) is a face-to-face event that serves as the heartbeat of the ART, aligning all the teams on the ART to a shared mission and vision. Backlog refinement (B) is the process of breaking down, estimating, and prioritizing the backlog items. ART syncs (D) are meetings that facilitate cross-team collaboration and alignment.

According to theStrategic Themesarticle on the Scaled Agile Framework website, strategic themes are portfolio-level business objectives that provide competitive differentiation and strategic advantage. They provide business context for portfolio strategy and decision-making, representing aspects of the enterprise's strategic intent. Strategic themes are best stated in Objective and Key Result (OKR) format. Written in plain business language, these OKRs say what the portfolio will pursue, thus providing decision-makers and contributors at all levels the clarity needed for decentralized decision-making. Therefore, the correct answer is D, create a 'one-stop shop' for all citizen-facing services provided by the agency. This is a good example of an agency strategic theme, as it expresses a clear and measurable goal that aligns with the agency's vision and mission. The other options are not accurate, as they are not good examples of agency strategic themes. Comply with agency development lifecycle regulations (A) is not a strategic theme, but a compliance requirement that applies to all solutions. Reduce agency IT spend (B) is not a strategic theme, but a cost-cutting measure that does not reflect the value proposition of the agency. Improve cost and schedule performance of IT projects is not a strategic theme, but a project management metric that does not capture the business outcomes of the solutions.

According to theGovernment Articleon the Scaled Agile Framework website, using firm fixed price contracts may significantly affect lead time for systems development. The article states that ''Firm fixed price (FFP) contracts are often used in government programs, but they are not well suited for Agile development. FFP contracts typically require detailed specifications and fixed scope, which are incompatible with the iterative and adaptive nature of Agile. FFP contracts also create a misalignment of incentives between the contractor and the government, as they reward the contractor for delivering the minimum acceptable solution, rather than the best possible value. FFP contracts also discourage collaboration and feedback, as any change in scope or requirements may trigger lengthy negotiations and contract modifications.'' Therefore, the correct answer is A, using firm fixed price contracts. The other options are not accurate, as they are not the types of decisions that may significantly affect lead time for systems development. Using relative size estimating (B) is a common Agile practice that helps teams plan and track their work. Approved budget, required development tools, and dedicated team members are enablers, not impediments, of systems development. Prioritizing the product backlog using WSJF (D) is a method of applying an economic view to optimize value delivery.

One benefit of Program Increment (PI) Planning is that it builds the social network on which the Agile Release Train (ART) depends1.PI planning is a face-to-face event that establishes communication and collaboration among all team members and stakeholders2.It fosters a sense of shared mission and vision, trust and respect, and collective ownership and accountability3.It also helps to create a culture of learning and innovation within the ART4.

1:PI Planning - Scaled Agile Framework2:The Ultimate Guide to PI Planning [2023 SAFe Edition] - Easy Agile3:Program Increment (PI) is the Heart of Scaled Agile Framework (SAFe)4:PI Planning - Scaled Agile Framework