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:

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