Card 1 of 36 Known: 0 / 36
click to reveal definition
click to flip back
You know 0 of 36 cards in current set.

Ready to get certified?

Get Certified

Need this expertise applied inside your organization?

Explore Our Services

Full Glossary

RTE Role

Release Train Engineer (RTE)
A servant leader and coach for the Agile Release Train. The RTE facilitates ART events and processes, helps teams deliver value, manages risks and dependencies, escalates impediments, and drives relentless improvement.
Servant Leadership
A leadership style central to the RTE: listening and supporting teams, creating an environment of mutual influence, coaching people to solve their own problems, and removing impediments rather than directing work.
RTE vs. Scrum Master
The RTE operates at the ART level, much as a Scrum Master/Team Coach operates at the team level. The RTE facilitates program-level events and coordinates across all teams on the train.
Coordinating with SoS / Coach Sync
The RTE facilitates the Scrum of Scrums / Coach Sync to coordinate dependencies, track progress toward PI objectives, and surface cross-team impediments, typically held one or more times per week.

ART & Value

Agile Release Train (ART)
A long-lived team of Agile teams (50–125 people) that, with stakeholders, incrementally develops, delivers, and operates one or more solutions in a value stream on a fixed PI cadence.
Organizing the ART Around Value
Designing the train so teams are cross-functional and able to define, build, test, and deploy value with minimal dependencies — aligning team structure to the flow of value in the value stream.
Stream-Aligned and Enabling Teams
Team topologies SAFe draws on: stream-aligned teams deliver value directly, while enabling teams (e.g., platform, complicated-subsystem) support them — concepts the RTE uses when shaping the ART.
ART Roles (RTE, PM, System Architect, Business Owners)
Key content and leadership roles on the train: RTE facilitates execution; Product Management owns the ART backlog and vision; System Architect guides architecture; Business Owners are accountable for value.

PI Planning

Program Increment (PI)
A timebox (typically 8–12 weeks) during which an ART delivers incremental value. The PI provides a development cadence and a regular planning and integration rhythm for the train.
PI Planning
The cornerstone event of the ART, where all teams plan together for the upcoming PI. The RTE is the chief facilitator, ensuring readiness, managing the agenda, and driving alignment and commitment.
Preparing for PI Planning
RTE responsibilities before the event: organizational readiness (strategy, alignment, teams), content readiness (vision, top features, briefings), and logistics readiness (facilities, tools, schedule).
Business Context & Vision Briefings
Opening PI Planning presentations where Business Owners share the business context and Product Management presents the vision and top features, giving teams the information needed to plan.
Draft Plan Review & Management Review
Mid-event checkpoints where teams present draft plans and the management review/problem-solving meeting adjusts scope, resolves bottlenecks, and makes business decisions before final planning.
PI Objectives & Business Value
Teams summarize their planned outcomes as PI objectives; Business Owners assign business value (1–10) in a collaborative conversation, aligning teams on priorities and enabling later measurement.
Program Board
A visualization produced in PI Planning showing features by iteration, cross-team dependencies, and milestones. The RTE uses it to manage dependencies throughout the PI.
Confidence Vote
A fist-of-five vote at the end of PI Planning where teams and the ART express confidence in meeting the PI objectives. Low confidence triggers re-planning before commitment.
ROAM Risk Management
During PI Planning, program risks are categorized as Resolved, Owned, Accepted, or Mitigated, making them visible and ensuring each has a clear disposition and owner.

Executing the PI

Develop on Cadence, Release on Demand
The ART develops on a fixed cadence of iterations and PIs while releasing value to customers whenever the business requires, decoupling the act of release from the development rhythm.
ART Sync (PO Sync + Coach Sync)
Recurring coordination events the RTE facilitates during the PI: the PO Sync aligns on scope/priorities and progress, and the Coach Sync/SoS addresses execution, dependencies, and impediments.
System Demo
An integrated demonstration of the new features from all teams on the ART, providing an objective measure of progress at the program level — ideally every iteration.
Innovation and Planning (IP) Iteration
A cadence-based iteration each PI providing time for innovation, learning, PI Planning, the Inspect & Adapt event, and a guard band that improves the predictability of the ART.
Managing Dependencies & Impediments
A core RTE duty: tracking cross-team and cross-ART dependencies on the program board, escalating systemic impediments beyond the train's authority, and protecting flow.

Continuous Delivery

Continuous Delivery Pipeline (CDP)
The flow of Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand that enables an ART to deliver value frequently and with low risk.
DevOps and CALMR
SAFe's DevOps mindset — Culture, Automation, Lean flow, Measurement, and Recovery — which the RTE champions to break silos and accelerate the flow of value through the pipeline.
Release on Demand
Releasing value to customers all at once, staggered, or on a steady stream, based on market and business needs, decoupled from the development cadence and enabled by deployment automation.

Continuous Improvement

Inspect & Adapt (I&A)
The significant event at the end of each PI combining a PI System Demo, quantitative and qualitative measurement, and a structured problem-solving workshop that produces improvement backlog items.
Problem-Solving Workshop
A structured root-cause analysis during I&A using techniques like the fishbone (Ishikawa) diagram and 5 Whys to identify systemic problems and define improvement actions for the next PI.
Improvement Backlog Items
Actionable items generated from the I&A workshop, fed into the ART backlog and committed in the next PI so the train relentlessly improves its way of working.
Communities of Practice (CoP)
Informal groups across the ART that share knowledge and improve practices in a domain (e.g., test automation, RTE/Scrum Master). The RTE fosters CoPs to spread learning.

Coaching the ART

Facilitating ART Events
The RTE skillfully facilitates large-group events using clear agendas, timeboxing, visualization, and decision techniques to keep dozens of people aligned, engaged, and productive.
Coaching Agile Teams & Leaders
The RTE coaches teams toward self-organization and high performance and coaches leaders and stakeholders to support the ART, model Lean-Agile behaviors, and remove organizational impediments.
Driving Relentless Improvement
The RTE continuously assesses ART health and flow, encourages experimentation, and uses metrics and retrospectives to make the train measurably better over time.

AI-Empowered RTE

AI for PI Planning Preparation
Using AI to accelerate readiness — drafting briefings, mapping likely dependencies, scoring risks, and summarizing inputs — so facilitation time focuses on alignment, commitment, and human judgment.
AI for Dependency & Risk Management
Applying AI to analyze the program board and team plans to surface hidden dependencies and emerging risks early, helping the RTE coordinate proactively across the train.
AI in Inspect & Adapt
Leveraging AI to aggregate flow and quality metrics, cluster retrospective themes, and support root-cause analysis, making the I&A problem-solving workshop faster and more data-driven.
Responsible AI Facilitation
The RTE ensures AI is used transparently and ethically across the ART — augmenting teams' decisions while keeping people accountable for outcomes, quality, and value.
Get started with ICON, today.
Book a consultation