The role of the System Architect/Engineer in SAFe is to guide the teams and support the Architectural Runway, which is the existing code, components, and technical infrastructure needed to implement near-term features without excessive redesign and delay. The System Architect/Engineer defines and communicates the technical and architectural vision for the solutions developed by an Agile Release Train (ART), ensuring that they fit the intended purpose and align with the enterprise and solution architecture. The System Architect/Engineer also collaborates with various roles, teams, and stakeholders within and outside the ART to ensure that the system architecture supports the evolving business needs and enables fast and reliable implementation.  References :  System Architect/Engineering - Scaled Agile Framework ,  Architectural Runway - Scaled Agile Framework

  The “C” in the CALMR approach to DevOps represents culture.  Culture is the first element of the CALMR mindset, which guides the ART toward achieving continuous value delivery by enhancing culture, automation, lean flow, measurement, and recovery 1 .  Culture refers to the shared values, beliefs, and behaviors that support collaboration, communication, and continuous improvement among the development, operations, security, and other teams involved in the value stream 2 .  Culture also includes respecting and empowering the people and teams, fostering a learning and growth mindset, and creating a customer-centric focus 3 .  Culture is the foundation of DevOps, as it enables the alignment and integration of the technical and organizational aspects of DevOps 4 . The other options are not what the “C” stands for in the CALMR approach to DevOps, although they are related to other elements of the mindset. Completion is not a specific term in the CALMR approach, but it could be associated with measurement, which tracks the progress and outcomes of the value delivery. Cycle-time is a metric that measures the time it takes to deliver value from idea to production, and it is influenced by lean flow, which optimizes the value stream and eliminates waste. Continuous integration is a technical practice that involves merging code changes frequently and automatically testing them, and it is part of automation, which reduces manual work and errors and accelerates feedback loops.  References :  CALMR - Scaled Agile Framework ,  The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut ,  Core Values - Scaled Agile Framework ,  CALMS DevOps : Defining 5 DevOps Principles | Cprime

 The Inspect and Adapt event is a significant event held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated by the train. Teams then reflect and identify improvement backlog items via a structured, problem-solving workshop. The Inspect and Adapt event consists of three parts: PI System Demo, Quantitative and qualitative measurement, and Retrospective and problem-solving workshop. The last part is where the practices of reflection, problem solving, and identifying improvement actions are demonstrated. The teams use a root cause analysis technique, such as the Five Whys, to identify the most critical impediments that impact their performance and quality. They then brainstorm and prioritize improvement actions that address the root causes and create SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) goals for implementing them in the next PI. The improvement actions are added to the Program Backlog and reviewed in the next PI Planning event.  References : =  Inspect and Adapt - Scaled Agile Framework ,  Scaled Agile Framework: Understand SAFe and Its 4 Core Values

According to the SAFe-for-Teams-SAFe-Practitioner-6-0 documents, enabler stories are short descriptions of a small piece of desired functionality that support exploration, architecture, infrastructure, or compliance. Among these four types of enabler stories, exploration is the one that is used for building and evaluating prospective solutions alternatives. Exploration enabler stories support research, prototyping, and other activities needed to develop an understanding of customer needs, including the exploration of prospective solutions and evaluation of alternatives. They help validate assumptions, reduce uncertainty, and increase the likelihood of building the right thing. Therefore, the correct answer is A. Exploration.  References :  Enablers - Scaled Agile Framework ,  Story - Scaled Agile Framework ,  Features, Capabilities, & Enablers - Productfolio

The Iteration Review is a regular SAFe Scrum event where the team inspects the iteration increment, assesses progress, and adjusts the team backlog. The purpose of the Iteration Review is to measure the team’s progress by showing working stories to the Product Owner and other stakeholders to get their feedback. The Iteration Review provides a way to gather immediate, contextual feedback from the team’s stakeholders on a regular cadence. The Iteration Review also allows the team to demonstrate their contributions, receive feedback to improve the solution, and adjust the Team Backlog based on new opportunities.  References :  Iteration Review ,  Iteration Review ,  What is Iteration review in SAFe® 6.0? ,  Iteration Review 65

Stories are the primary means of expressing needed functionality in SAFe. They largely replace the traditional requirements specification with new paradigms based on Lean-Agile development. Stories are elaborated by a user-voice statement and acceptance criteria, and they are used to describe the features and behaviors of the system at various levels of abstraction. Stories are also testable, estimable, and prioritizable, which makes them suitable for planning and delivering value in an iterative and incremental way.  References :  SAFe Requirements Model ,  What replaces detailed requirements documents in agile? ,  What replaces detailed requirements documents in SAFe?

 The Agile Release Train (ART) is a long-lived team of Agile teams that incrementally develops, delivers, and often operates one or more solutions in a value stream 1 . The ART aligns teams to a common mission using a single Vision and a Program Backlog. The Vision is a description of the future state of the solution under development.  It reflects customer and stakeholder needs, as well as the features and capabilities planned for the solution 2 . The Program Backlog is the single source of truth for the upcoming features of the system.  It contains the enablers necessary to build the Architectural Runway, as well as the user and business features that deliver customer value 3 . The Vision and the Program Backlog provide the context and the content for the ART to plan, commit, develop, and deploy together.  References :  Agile Release Train - Scaled Agile Framework ,  Vision - Scaled Agile Framework ,  Program Backlog - Scaled Agile Framework

The Agile Release Train Sync is a weekly meeting where the Release Train Engineer (RTE), Product Management, System Architect/Engineering, and Product Owners (POs) coordinate and communicate the current state of the Agile Release Train (ART). The POs provide visibility into the analysis, approval, and Feature readiness for implementation, which are the key aspects of managing the Program Backlog. The POs also share any dependencies, risks, or impediments that may affect the delivery of value by the ART. The Agile Release Train Sync helps align the teams and stakeholders on the vision, roadmap, and priorities of the solution.  References :  Agile Release Train ,  Product Owner ,  Program Backlog

Guiding investments by horizon is one of the four Lean budget guardrails that describe the policies and practices for budgeting, spending, and governance for a specific portfolio.  This guardrail helps ensure that the portfolio allocates its budget to solutions that reflect different time horizons and risk profiles, balancing near-term opportunities with long-term strategy and growth 1 .  The portfolio-level guidance for investments by horizon is based on the four horizons model 2 , which categorizes solutions into four types: Horizon 0 (solutions that are being decommissioned), Horizon 1 (solutions that are mature and generate most of the current revenue), Horizon 2 (solutions that are emerging and have high growth potential), and Horizon 3 (solutions that are exploratory and have high uncertainty).  Each value stream should allocate its budget to solutions in these horizons according to the portfolio’s vision and roadmap 1 .  References :  1 :  Lean Budget Guardrails - Scaled Agile Framework 2 :  Investment Horizons - Scaled Agile Framework

A component team is an Agile Team whose primary area of concern is focused on a specific component, or set of components, of the system. They leverage their technical skills and interest and focus on building robust components that provide for reliability, separation of concerns, foster re-use, and improve testability. Component teams are typically used when the system has complex, nonfunctional requirements that require deep technical expertise and specialization, such as performance, security, scalability, etc. Component teams can also enable high reuse of components across multiple solutions, reducing duplication and waste. However, component teams also introduce challenges, such as increased dependencies, coordination, and integration efforts with other teams, as well as reduced end-to-end value delivery and customer feedback. Therefore, component teams should be used sparingly and only when the benefits outweigh the costs.  References :  Organizing Agile Teams and ARTs: Team Topologies at Scale ,  Agile Teams ,  Feature Teams vs Component Teams ,  System Team ,  Feature Team vs Component Team in Agile