Close this search box.
Close this search box.
Close this search box.

Building Great Release Train Engineers – a talk with Mattias & Yuval


In the scaled Agile framework, one key role is the Release Train Engineer (RTE). But who should I look for to fill this role? What are the first few process improvements experienced RTEs typically do? Yuval Yeret (AgileSparks) and Mattias Skarin (Crisp) took the time to discuss the traits of a good RTE.

What are the traits of a good RTE?

Yuval: The easy answer to this question is that you are looking for a Scrum master for a team of teams. Going beyond that, when it comes to specific traits, you are looking for someone who cares about process and improvements, someone who has the ability to orchestrate things. But at the same time, someone who also knows when to step back and let the teams organize themselves. A good RTE is a great communicator and can see and understand what is happening.

Mattias: Firstly, a good RTE should be a people person, someone you’d like to talk to and bounce ideas with. Someone who builds trust and energy with their presence. In essence, a good RTE is the Uber Scrum master across teams. Secondly, a good RTE is systematic and makes sure the process events are run and planned in advance. Thirdly, a good RTE should be a good problem solver.

Let’s be even more specific, if you narrowed it down to three, which are the top 3 traits of a good RTE?

Yuval: Then I would say, (1) Someone who can be a coach and a servant leader; (2) someone who knows how to bring people together who work well together; and (3) someone who is passionate about improving things.Mattias: I would pick a people person, who is also systematic, and a good problem solver.

Name 3 things an RTE should do.

Yuval: The key task is to facilitate the Agile release train events. (for example PI planning, Art sync, Inspect & Adapt workshop). Over time, a good RTE builds in the capability in the release train to do more and more on their own. Finally, the RTE should facilitate the removal of obstacles and risks. He or she does not necessarily need to solve them all by himself, but rather, make them transparent and make sure that the most important ones are being tackled.

Mattias: I will concur with Yuval here. The part I would add is the focus on relentless improvement, always trying to make things a little bit better.

So on to improvements. Which event ‘that keeps the train on the tracks is the most common for companies to adjust to after running SAFe for a while?

Yuval: An early step is normally making the PI planning (Big Room Planning) more concise, such that you can run it in a day. This could happen through the removal of dependencies or by simplifying specific activities. One example would be making the draft plan review more fun, and less sequential. The final part I see RTE tweak is the Inspect & Adapt workshop. There are a few emergent patterns here: let people organize into teams according to the problems they want to see solved or, run it as an open space.

Mattias: Early tweaks include making the PI planning run successfully within a day and improving the quality for feature candidates entering the Big Room Planning (through adding and keeping a definition of “Ready”).

I know you are coming to Crisp in November to run the Advanced RTE training class. Who is the class for and what can I expect to learn?

Yuval: The class is for you as an RTE who has been running your own Agile release train for a couple of increments. We don’t go through the basics in this class. By grounding the participants in the Lean/Agile principles, we teach tips and tricks to the RTEs. For example, how to adapt the PI planning but at the same time stay aligned with the principles of Systems Thinking, Presume variability, and Preserve options. The goal is to inspire and build the RTE’s confidence to go beyond and adjust the basic practices, knowing they are well grounded on principles.
In this class, we expect RTEs to share knowledge and best practices so you can learn from each other (you probably have a few tips and tricks up your sleeve) in addition to picking up nuggets from the trainer.

Will we spend time on discussing what RTEs find challenging in their company?

Yuval/Mattias: Yes! There will be time set aside for this. And during the course, there will be plenty of time to engage with Yuval (trainer) and Mattias (host) who both are experienced Agile trainers in Scaled Agile scenarios.

This article was originally posted on the Crisp blog. If you’re not familiar with it, it is one of our must-read Agile blogs. We are proud to be collaborating with Crisp on bringing high-quality pragmatic SAFe training to Sweden.

Subscribe for Email Updates:



Implementation of Lean and Agile
Program Increment
Kanban 101
Lean-Agile Software Development
Product Management
Kaizen Workshop
What Is Kanban
Agile Games
Agile for Embedded Systems
Manage Budget Creation
Games and Exercises
Hybrid Work
Agile Techniques
Agile Outsourcing
Lean Agile Management
Agile in the Enterprise
Nexus Integration Team
Kanban Game
Jira Cloud
Sprint Iteration
Applying Agile Methodology
Enterprise DevOps
Scrum Primer
Kanban Basics
ALM Tools
Lean Budgeting
A Kanban System for Software Engineering
Agile Development
Lean Startup
AI Artificial Intelligence
Artificial Intelligence
Advanced Roadmaps
Development Value Streams
Jira admin
Nexus and Kanban
Limiting Work in Progress
Sprint Planning
Iterative Incremental Development
lean agile change management
speed @ scale
Agile Mindset
Principles of Lean-Agile Leadership
ART Success
Product Ownership
Acceptance Test-Driven Development
Continuous Deployment
Coaching Agile Teams
Continuous Improvement
Agile Marketing
Agile Contracts Best Practices
Lean Agile Leadership
Kanban Kickstart Example
Achieve Business Agility
Managing Risk on Agile Projects
System Team
System Archetypes
Legacy Enterprise
Rapid RTC
SAFe Release Planning
Business Agility
Agile Community
System Integration Environments
Agile India
Agile Delivery
Implementing SAFe
PI Planning
Nexus and SAFe
The Agile Coach
IT Operations
Operational Value Stream
SAFe DevOps
An Appreciative Retrospective
Jira Plans
Professional Scrum with Kanban
Elastic Leadership
Agile Risk Management
Lean Agile Basics
Scaled Agile Framework
Agile Project Management
Agile Product Development
Agile Basics
Lean and Agile Principles and Practices
Introduction to ATDD
Scrum Values
PI Objectives
Legacy Code
Lean Risk Management
Lean Software Development
Effective Agile Retrospectives
Daily Scrum
Lean and Agile Techniques
Professional Scrum Product Owner
Continuous Integration
Release Train Engineer
Story Slicing
Engineering Practices
Agile and DevOps Journey
Scrum Guide
Risk Management in Kanban
Agile Release Management
Accelerate Value Delivery At Scale
Agile Games and Exercises
Entrepreneurial Operating System®
Lean Agile
Systems Thinking
RTE Role
Change Management
Process Improvement
Quality Assurance
Perfection Game
Agile Testing Practices
Risk Management on Agile Projects
Agile Israel Events
Introduction to Test Driven Development
Lean-Agile Budgeting
Agile Exercises
Certified SAFe
Software Development Estimation
Scrum Master Role
speed at scale
Releases Using Lean
Sprint Retrospectives
Built-In Quality
Test Driven Development
Scrum and XP
Agile Project
Portfolio for Jira
Professional Scrum Master
ScrumMaster Tales
Agile Product Ownership
Risk-aware Product Development
Scrum Master
Nexus vs SAFe
Managing Projects
Scrum With Kanban
Reading List
Software Development
Large Scale Scrum
Agile Israel
Lean Agile Organization
Agile Release Planning
Continuous Delivery
Agile Assembly Architecture
The Kanban Method
Value Streams
Continuous Planning
Pomodoro Technique
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart