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

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

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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:

Categories:

Tags:

Lean-Agile Budgeting
Agile Israel
Process Improvement
Agile Testing Practices
AI
ALM Tools
Sprint Iteration
Change Management
Sprint Planning
Agile Exercises
PI Planning
Presentation
Keith Sawyer
AgileSparks
Jira Cloud
agileisrael
predictability
Achieve Business Agility
The Agile Coach
Agile in the Enterprise
Agile Project
Jira admin
Scrum Guide
EOS®
TDD
Nexus and SAFe
Scrum
Risk Management in Kanban
Agile Release Planning
Kanban 101
Coaching Agile Teams
Code
RSA
Limiting Work in Progress
Applying Agile Methodology
LPM
The Kanban Method
Continuous Improvement
Scrum Master
GanttBan
What Is Kanban
speed @ scale
speed at scale
Built-In Quality
AI Artificial Intelligence
Kanban Basics
Reading List
Lean Agile Basics
Introduction to Test Driven Development
Scrum and XP
Kanban
Continuous Planning
ROI
lean agile change management
Atlassian
Releases Using Lean
Professional Scrum Product Owner
Portfolio for Jira
Lean Agile Management
Agile Mindset
Kanban Kickstart Example
Lean Budgeting
Risk Management on Agile Projects
Agile
Agile Development
Quality Assurance
RTE
Agile Product Ownership
Agile Outsourcing
Elastic Leadership
LeSS
Agile and DevOps Journey
System Team
Lean Software Development
Entrepreneurial Operating System®
Scrum Primer
Scrum Master Role
Kaizen
Managing Projects
Daily Scrum
Large Scale Scrum
Jira Plans
DevOps
Agile Israel Events
Certified SAFe
Engineering Practices
Release Train Engineer
QA
Professional Scrum Master
Frameworks
Agile Techniques
Enterprise DevOps
Agile Project Management
Continuous Delivery
Operational Value Stream
Implementing SAFe
Value Streams
Self-organization
LAB
Nexus
User stories
Lean and Agile Techniques
Story Slicing
Product Ownership
IT Operations
Test Driven Development
ARTs
Legacy Enterprise
Video
Team Flow
chatgpt
Atlaassian
Introduction to ATDD
Advanced Roadmaps
SA
Nexus and Kanban
Agility
Planning
Kaizen Workshop
Implementation of Lean and Agile
Scaled Agile Framework
Agile Community
Certification
Tools
Effective Agile Retrospectives
Agile Contracts Best Practices
System Archetypes
Lean and Agile Principles and Practices
Program Increment
SPC
WIP
An Appreciative Retrospective
Development Value Streams
Agile Product Development
Agile Risk Management
System Integration Environments
Agile Assembly Architecture
Agile Games
Agile for Embedded Systems
ATDD vs. BDD
Lean-Agile Software Development
POPM
ART Success
PI Objectives
Artificial Intelligence
Acceptance Test-Driven Development
BDD
SAFe
Games and Exercises
Scrum With Kanban
Agile Program
Continuous Integration
Lean Agile Leadership
Risk-aware Product Development
Agile Games and Exercises
Slides
Lean Startup
Nexus vs SAFe
Pomodoro Technique
Kanban Game
Continuous Deployment
Agile India
Webinar
Agile Release Management
Agile Marketing
Systems Thinking
Manage Budget Creation
ScrumMaster Tales
Lean Agile Organization
Legacy Code
SAFe DevOps
Hybrid Work
NIT
Scrum.org
Jira
Managing Risk on Agile Projects
Agile Basics
Principles of Lean-Agile Leadership
ATDD
Tips
Amdocs
Agile Delivery
Professional Scrum with Kanban
RTE Role
SAFe Release Planning
Lean Agile
Iterative Incremental Development
Perfection Game
Spotify
Sprint Retrospectives
Software Development Estimation
Accelerate Value Delivery At Scale
Product Management
Lean Risk Management
Rapid RTC
Software Development
Covid19
Nexus Integration Team
Business Agility
A Kanban System for Software Engineering
AgileSparks
Logo
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