SAFE-RTE Practice Questions

An effective Scrum Master understands customer needs, which is crucial for guiding the team

towards delivering value that meets or exceeds customer expectations. This focus on the customer

ensures that the team's efforts are aligned with the end goal of satisfying customer requirements

and achieving business objectives.

The core value of Transparency in SAFe is key to creating an environment where “facts are always

friendly.” This is because transparency encourages an open culture where information is shared

openly, and everyone has access to the facts, which allows for better decision-making and fosters

trust within the organization. The SAFe Core Values page explains that transparency is one of the four

core values that guide the behaviors and actions of everyone participating in a SAFe portfolio. It

emphasizes that work and decisions must be visible, debated, resolved, and transparent to ensure

alignment and enable the building of trust through a culture where facts can be discussed openly1.

The Core Competency of Business Agility that includes aligning strategy with execution is Lean

Portfolio Management. This is verified by the information provided on the SAFe website, which

states that Lean Portfolio Management aligns strategy and execution by applying Lean and systems

thinking approaches to strategy and investment funding, Agile portfolio operations, and

governance 1. This competency enables organizations to align their strategy to execution, ensuring

that they create and maintain a portfolio of investments that align with the enterprise’s strategic

objectives and meet the customer’s needs. It involves collaboration between the portfolio

stakeholders and Agile Release Trains (ARTs) to develop and implement the strategic themes and

Lean budgets that guide the portfolio.

In the SAFe work item hierarchy, Features are indeed decomposed into Stories. This is supported by

the information found in the SAFe Requirements Model, which outlines that a Feature is described

by a phrase, benefit hypothesis, and acceptance criteria, while a Story is elaborated by a user-voice

statement and acceptance criteria. These artifacts replace the traditional system and requirements

specifications with new paradigms based on Lean-Agile development. Stories are the primary artifact

used to define system behavior in Agile and are short, simple descriptions of functionality told from

the user’s perspective and written in their language. Each implements a small, vertical slice of

system behavior. The detailed implementation work is expressed through stories, which comprise

the Team Backlog12.

The Iteration Retrospective is a regular event where Agile teams reflect on the completed iteration

to derive new ideas and identify ways to improve their process. This reflection is aligned with the

concept of relentless improvement, which is a core value of SAFe. The retrospective aims to uncover

what worked well, what did not, and what the team can do better in the next iteration1.

During the Iteration Retrospective, teams discuss the results of the iteration, review their practices,

and create improvement stories for the next iteration. Inputs to this event may include iteration

goals, the team’s increment, a list of improvement stories identified, and the actions taken since the

last retrospective, as well as a collection of agreed-to iteration metrics. The outputs of a successful

Iteration Retrospective include the creation of a few improvement stories and an updated Team

Backlog1.

The process involves the entire team, facilitated by the Scrum Master/Team Coach, who introduces

the goals, agenda, and format of the retrospective. The team then reviews and discusses the metrics

they have agreed upon and determines any actions to take. Team members may write their thoughts

on a flip chart or a digital tool designated for the retrospective. Popular formats for qualitative

feedback include individual note-taking, appreciation notes, conceptual words, rating scales, and

simple open discussions recorded under headings of what went well, what did not, and what to do

better next time

The ART Sync event is a combination of PO-sync and Scrum of Scrums events. It is used to coordinate

progress across the Agile Release Train, involving Scrum Masters/Team Coaches, Product Owners,

and other select team members to discuss progress, impediments, scope, and priority adjustments.

Release Train Engineers (RTEs) have the opportunity to regularly practice and improve the skill of

servant leadership. This skill is central to the RTE role in the SAFe framework, as RTEs are expected to

be servant leaders and coaches to their Agile Release Trains (ARTs).

Servant leadership involves focusing on the needs of others, especially team members, before

considering one’s own. It requires the leader to ensure that other people’s highest priority needs are

being served to encourage teamwork and personal involvement. An RTE practicing servant

leadership will:

1. Facilitate and Support: Help teams navigate through the SAFe processes, removing impediments

and fostering an environment where teams can be effective1.

2. Coach and Mentor: Provide guidance to teams, Scrum Masters, and other stakeholders in Lean-

Agile practices and mindsets1.

3. Lead by Example: Demonstrate the principles of Lean-Agile leadership, embodying the values and

principles of SAFe in their daily work1.

4. Drive Continuous Improvement: Encourage and lead the efforts for relentless improvement within

the ART, promoting a culture of innovation and continuous learning1.

5. Communicate and Align: Ensure that everyone on the ART understands the mission, vision, and

goals, and is aligned in their efforts to achieve them1.

By regularly practicing and improving their servant leadership skills, RTEs can effectively lead their

ARTs to deliver value more efficiently and foster a healthy, collaborative, and high-performing team

environment.

To embrace relentless improvement and a growth mindset as an individual, an RTE might:

Identify Personal Challenges: Recognize areas of personal development and challenges that need

attention1.

Create Personal Actions: Develop a plan of action to address these challenges and improve upon

them1.

Engage in Continuous Learning: Commit to lifelong learning and continuously seek opportunities to

grow both personally and professionally1.

Foster a Culture of Feedback: Seek and provide feedback regularly to continue the journey of

personal and professional development1.

Coach with Powerful Questions: Use coaching techniques such as powerful questioning to facilitate

self-discovery and growth1.

By focusing on these areas, an RTE can maintain a growth mindset and continuously strive for

personal and professional improvement.

Product Management is responsible for defining and supporting the building of desirable, feasible,

viable, and sustainable products that meet customer needs over the product-market lifecycle. To do

this effectively in a SAFe environment, they must collaborate with various stakeholders to determine

the capacity allocation for upcoming Enabler work.

Enabler work refers to the activities that support the development of business features, such as

exploration, architecture, infrastructure, and compliance. These are necessary to advance the

Solution and build its architectural runway. The capacity allocation for Enabler work is a collaborative

effort between Product Management, System Architects/Engineering, and other stakeholders. This

ensures that sufficient capacity is allocated for both feature and enabler work, balancing the need to

address technical debt, architectural advancements, and other necessary activities that enable future

delivery of value.

The SAFe framework suggests a ‘capacity allocation’ approach where a certain percentage of the

team’s capacity is allocated to Enabler work. This is not a fixed number but rather a guideline to

ensure that teams invest in necessary work that may not directly deliver new customer features but

is essential for the long-term health and adaptability of the product. By establishing a capacity

allocation for Enabler work, Product Management ensures that there is a balance between delivering

new features and maintaining the technical quality and flexibility of the product to adapt to future

changes. This approach helps in managing the investment in Enabler work and ensures that it is not

overlooked in the pursuit of immediate feature delivery.

DevOps is defined within the SAFe framework as a mindset, a culture, and a set of technical

practices. It is not just a set of tools or a single process, but rather a combination of cultural

philosophies, practices, and tools that increases an organization’s ability to deliver applications and

services at high velocity. This definition aligns with option C, which emphasizes the importance of

close cooperation between development and operations teams to provide value to the customer.

The SAFe framework further elaborates that DevOps is part of the Agile Product Delivery

competency and is essential for a Continuous Delivery Pipeline (CDP). It helps break down

organizational silos and enables the fast flow of planned work into production, while achieving

stability, reliability, availability, and security. The goal of DevOps is to deliver value whenever there is

a business need, and it is supported by the CALMR approach—Culture, Automation, Lean-flow,

Measurement, and Recovery—which guides the implementation of DevOps in a SAFe enterprise1.