Scaled Agile Framework (SAFe) Architect Practice Test

Disable ads (and more) with a membership for a one time $4.99 payment

Prepare for the SAFe Architect Test with carefully curated flashcards and multiple choice questions. Each question includes hints and explanations. Excel in your exam preparation!

Practice this question and more.


A System Architect is working with a new Agile Release Train (ART) and has planned multiple Enabler Features. How should the System Architect approach a concerned Product Manager about capacity?

  1. Negotiate capacity allocation for Enabler work

  2. Refer the Product Manager to the Enterprise Architect

  3. Discuss the need to assume variability

  4. Acknowledge the concern and remove the Enablers

The correct answer is: Discuss the need to assume variability

The correct answer involves discussing the need to assume variability. In a SAFe environment, it is essential for the System Architect to communicate about the uncertainties and variations that can arise during the implementation of Enabler Features. These Enabler Features are designed to help the ART build out necessary infrastructure, compliance, or architectural improvements, which are crucial for the success of future features and overall product quality. Assuming variability means recognizing that early estimates of capacity can change as more information becomes available. By discussing this concept, the System Architect can help the Product Manager understand that not all aspects of the work can be perfectly predicted at the outset. Regularly revisiting these capabilities allows for adjustments based on accumulated knowledge from ongoing development, ultimately leading to a more flexible and adaptive approach to managing capacity within the ART. This dialogue fosters an environment where both the System Architect and Product Manager can engage in productive discussions about prioritization and resource allocation, making it easier to balance immediate concerns with long-term objectives. Basic discussions and assumptions about capacity are part of Agile’s inherent principles of collaboration and iterative improvement, allowing teams to navigate complexities in an adaptive manner.