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:

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