SAFe-RTE SAFe Release Train Engineer (RTE) Question and Answers

Capabilities are in the Program Backlog

Features are in the Program Backlog

Stories are in the Solution Backlog

System Demo

Scrum of scrums

Cumulative flow diagram

Team status report

Capacity and load estimates

(Correct)

Program delivery schedule

Draft PI Objectives

Risks and impediments

Iteration Goals

Refined team backlogs

Determine the RTE's capacity for attending meetings and do not exceed it

Make status available at the end of every other Iteration rather than every Itera-tion

Delegate some program reporting and meeting attendance to Scrum Masters on the train

Encourage interested parties to attend the System Demo

PI Objectives

Iteration goals

Team Backlog

Iteration backlog

Program Backlog

Ishikawa diagrams

Team velocity Metrics

Business context

Cumulative flow diagrams

Product/Solution Vision

Architecture Vision and development practices

The T-shirt sizes for each of the Features

The actual business value of each Feature

Feature size expressed in story points

Job size based on relative estimation

Drive teams to specific outcomes

Provide answers about Features

Coach leaders to increase alignment

Encourage teams to self-organize

Manage dependencies for teams

To measure the team's capacity to load ratio

To increase predictability

To collect team performance metrics

To improve quality

To gauge team predictability

Instruct the Scrum Master to resize the Story

Continue to support the team's decision on sizing

Suggest the team stop the sizing of the User Story and add it to the next lteration as-is

Coordinating with other teams

Owning the daily stand-up

Facilitating the Scrum of Scrums

Prioritizing the Team Backlog

Encourage discussion of each team's product Vision as part of the final plan re-view

Verify that each team's uncommitted objectives have lower business value than the committed PI Objectives in order to reflect proper prioritization

Facilitate the ROAMing of each team's risks

Facilitate all teams when they are presenting their final plans to the entire Agile Release Train

To align the team members and the Product Owner to the mission

To hold the team accountable to their Pl Objectives

To summarize the business outcomes an Agile Team intends to achieve during the Program Increment (PI)

The DoD is not used by the teams because it is used as a method to manage tech-nical debt across the ART

At the higher levels there is only one DoD for everything that passes through the Agile Release Train to a Solution increment or a release

The teams share one common DoD

The DoD should evolve as system capabilities evolve

Releasing, Continuous Integration, and planning

Innovation, planning, and an estimating guard band

Iteration Planning, User Story refinement and estimating

Estimating techniques, training, and innovation

Development and Operations teams work together

The process is visible to all stakeholders

The team is constantly improving its process

Team members must immediately share any and all feedback with each other

Provide subject matter expertise

Lay out the team's plan for the iteration

Encourage the team to learn from their mistakes

Set long-term goals for the team

Focus on deadlines and technical options

Gives open, honest opinions

Removes all conflict

As a technical expert

Understands customer needs

Team Features, Stories, and team-level enablers

Changes to capacity and load, final PI objectives, program risks and impediments

Changes to iteration goals, measured velocity, and dependencies

Planned Features, uncommitted objectives, and ROAMed risks

To ensure that the SAFe House of Lean is reflected in standard operating proce-dure

To build an understanding of why the lean-agile practices work

To make sure that no modifications are made by the adopters of SAFe

To maintain a central control of key decision-making

How the Kanban work in process limits are set

How to achieve objectives

How teams plan the implementation

Facilitate team problem-solving

Focus on business value delivery

Drive toward specific outcomes

Fix problems for the team

Ask the team for the answer

Focus on deadlines

Enabler Epics

Enabler Features

Enabler Capabilities

Enabler Stories

That the feature can be completed by that team independently

That the team has not broken the feature into stories yet and has not identified dependencies

That it has dependencies on teams in other Agile release trains (ARTs) or Solution Trains

That the team has been assigned, but the feature’ uépendencies have not been identified yet