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.

According to the Essential SAFe article on the Scaled Agile Framework website, the Product Owner (PO) is the role in SAFe that has content authority over the Agile Team’s backlog. The article states that “The Product Owner (PO) is the content authority for the team backlog. The PO is responsible for defining stories and prioritizing the backlog.” Therefore, the correct answer is B, Product Owner. The other options are not accurate, as they are not the roles that have content authority over the Agile Team’s backlog. The Release Train Engineer (A) is the servant leader and chief Scrum Master for the Agile Release Train (ART). The Product Management © is the content authority for the program backlog. The Agile Team (D) is the cross-functional group of developers, testers, and other specialists that deliver value in an iteration.

According to the Applying Lean Estimating and Forecasting in Cadence article on the Scaled Agile Framework website, ART velocities are used to conduct ‘what if’ analysis for estimating and forecasting in SAFe. The article states that “The ART velocity is used to conduct ‘what if’ analysis, which helps determine the feasibility of the plan and the number of features that can be delivered in a PI. The ART velocity is also used to forecast the delivery of features and capabilities beyond the current PI.” Therefore, the correct answer is C, ART velocities are used to conduct ‘what if’ analysis. The other options are not accurate, as they are not the statements that are true for estimating and forecasting in SAFe. Feature estimation is not independent of team-level input (A), as teams are involved in estimating the size and complexity of features using story points or normalized story points. Epics are not estimated by the Epic Owner (B), as they are estimated collaboratively by the Epic Owner, Enterprise Architect, and Lean Portfolio Management. Work breakdown structure to the task level does not help increase estimation accuracy (D), as it introduces unnecessary overhead and delays feedback.