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:

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