Scaled Agile SAFe Release Train Engineer (6.0) SAFe-RTE Exam Questions

Answer : A, B

According to the SAFe framework, the Scrum Master's role is primarily that of a servant leader and coach for the Agile Team. They are responsible for helping educate the team in Scrum, Extreme Programming (XP), Kanban, and SAFe, ensuring that the agreed Agile process is followed.They also help remove impediments and foster an environment for high-performing team dynamics, continuous flow, and relentless improvement1.

Estimating stories is typically a collaborative effort among all team members during backlog refinement or iteration planning. The Scrum Master facilitates this process but does not estimate the stories for the team.This is because the team members who will be doing the work are best positioned to estimate the effort required1.

Assigning stories to team members also falls outside the Scrum Master's responsibilities. In SAFe, teams are self-organizing, meaning they decide among themselves who will work on which stories.The Scrum Master may facilitate discussions to help the team make these decisions, but they do not assign work to individual team members1.

Facilitating backlog refinement, facilitating the team's Innovation and Planning event, and coaching the team are all within the Scrum Master's responsibilities.They play a key role in these areas to support the team's progress and continuous improvement within the SAFe framework1.

Answer : B

The Release Train Engineer (RTE) is a servant leader whose responsibilities include facilitating ART events and processes, and supporting teams in delivering value.They help manage risks, escalate impediments, and drive relentless improvement1.

During Program Increment (PI) execution, when the System Team is unclear about how to test some of the larger Features, the RTE should encourage collaboration between the System Team and Product Management.This is because the RTE's role is to facilitate problem-solving by bringing together the necessary parties to find solutions, rather than allowing problems to escalate or directing others to solve them1.

The RTE's approach to this situation would typically involve:

Identifying the Impediment: Recognizing that the System Team's uncertainty about testing is an impediment to progress.

Facilitating Collaboration: Arranging a meeting between the System Team and Product Management to discuss and resolve the testing challenges.

Encouraging Problem-Solving: Guiding the discussion to ensure that it is focused on finding practical solutions for testing the Features.

Supporting Implementation: Once a solution is agreed upon, the RTE would assist in implementing the solution and ensuring that it is effectively integrated into the PI execution process.

This approach aligns with the RTE's responsibility to facilitate processes and support teams, ensuring that value is delivered and continuous improvement is achieved within the ART1.

Answer : B

During PI Planning in SAFe, it is the responsibility ofProduct Managementto provide the Agile Release Train (ART) context and Vision. The PI Planning event includes a presentation of business context and vision, which is typically delivered by Product Management. This aligns all teams on the ART to a shared mission and vision, which is essential for the planning process.The Release Train Engineer (RTE) facilitates the event, but it is Product Management that presents the vision and context for the upcoming Program Increment (PI)12.

Answer : D

A Release Train Engineer (RTE) uses an Iteration and Program Increment (PI) Calendar to visualize the Agile Release Train's cadence and synchronization. This calendar is a critical tool in SAFe for planning and tracking the events and milestones of a PI. It helps in aligning the team with the ART's schedule, ensuring that all teams are working in sync and that key events such as PI Planning, Iterations, and Inspect and Adapt sessions are conducted at regular intervals.The calendar serves as a visual aid to manage the flow of value through the ART by providing a clear view of the PI timebox, which typically includes four development Iterations followed by one Innovation and Planning (IP) Iteration1.By using this calendar, the RTE can facilitate a smooth and coordinated execution of the PI, which is essential for achieving the goals set out in the PI Objectives23.

Answer : D

In the SAFe framework, a Scrum Master exemplifies servant leadership by using persuasion rather than authority to lead the team. This approach aligns with the core principles of servant leadership, which emphasize serving the team, fostering collaboration, and empowering team members to self-organize and self-manage.

A Scrum Master who uses persuasion instead of authority:

Encourages the team to collaborate on solutions and respects their ability to self-manage.

Helps the team to understand the 'why' behind decisions and actions, which promotes buy-in and commitment.

Facilitates discussions that lead to consensus and shared understanding, rather than dictating terms or solutions.

Empowers team members to take ownership of their work and the processes they follow, leading to a more engaged and motivated team.

This behavior is crucial for creating a high-performing Agile team that is capable of navigating complex challenges and delivering value effectively.By focusing on persuasion, a Scrum Master supports the team's growth and development, ensuring that they are equipped to achieve their goals within the SAFe framework1.

Answer : B, D, F

To support a Continuous Integration (CI) culture, it's essential to focus on practices that promote frequent integration, visibility, and prompt resolution of integration issues. The three actions that align with these principles are:

Ensure fixing a failed integration attempt is always the top priority: When an integration fails, it should be addressed immediately. This practice helps maintain the health of the CI environment and ensures that new changes are always being integrated into a stable baseline.

Integrate often: Frequent integration of code changes helps in identifying conflicts and issues early, which reduces the complexity of resolving them. It also allows for quicker feedback and more rapid iteration on the development work.

Make integration results visible: Transparency is key in a CI culture. By making integration results visible to all team members, it encourages collective ownership of the codebase and the CI process. It also allows for faster detection and resolution of integration issues.

These actions are foundational to creating a robust CI culture, which is a critical aspect of the Continuous Delivery Pipeline in SAFe.They help ensure that the system is always in a potentially deployable state, even during development, which is a core principle of Agile methodologies1.

Answer : A

According to the SAFe framework, Agile Teams should allocate time for innovation continuously throughout the Program Increment. This is facilitated through the Innovation and Planning (IP) Iteration, which is a dedicated iteration that occurs every Program Increment (PI).It provides an estimating buffer for meeting PI Objectives and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt (I&A) events1.

The IP Iteration serves as a regular, cadence-based opportunity for teams to engage in innovation and learning activities that are difficult to fit into a continuous, incremental value delivery pattern. This iteration allows for activities such as hackathons, where individuals can work on innovative ideas outside the usual constraints of their regular backlog and team construct.The outcomes from these hackathons often make their way into the ART Backlogs, driving innovations that benefit the business1.

Furthermore, dedicating time to PI events during the IP Iteration ensures that the velocity of regular iterations is not reduced.This approach also enhances the predictability of PI performance and provides a buffer for meeting PI objectives1.