SAFe Principles Flashcards

What should the Release Train Engineer do during the final plan review on Day two of Program Increment (PI) Planning

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

The Release Train Engineer's core function is facilitation, not evaluation or decision-making. During the Day 2 final plan review, the RTE's job is to facilitate each team as they present their plans to the full Agile Release Train. ROAMing of risks occurs during the planning days themselves, not during the final review. Reviewing business value prioritization is the responsibility of Business Owners, not the RTE.

Program Increment (PI) Objectives should be written in the SMART format. What does the "R" in smart stand for?

Answer: Realistic

SMART is an acronym standing for Specific, Measurable, Achievable, Realistic, and Time-bound. The 'R' represents Realistic, meaning the objective must be grounded in what is actually attainable given current resources and constraints. The other options — Rationalized, Random, and Required — are not part of the SMART framework and do not describe the quality that the 'R' criterion is designed to ensure.

Why would a Release Train Engineer use an Iteration and Program Increment Calendar?

Answer: To visualize the Agile Release Train's cadence and synchronization

The Iteration and PI Calendar is a visual planning artifact that communicates the ART's cadence — the predictable rhythm of iterations, PI boundaries, and key ceremonies — and how teams synchronize with one another across the train. It is not designed to calculate cycle time, produce business value reports, or schedule around external non-SAFe events. Its primary purpose is making the train's coordination visible so all teams stay aligned.

Who can the Release Train Engineer work with to help eliminate policies and procedures that demotivate employees?

Answer: Lean-Agile Leaders

In SAFe, Lean-Agile Leaders are the specific role responsible for modeling Lean-Agile principles, coaching teams, and driving organizational culture change — including removing policies and practices that demotivate employees. Business Owners, Product Management, and Portfolio Managers focus on business value, product direction, and portfolio strategy respectively, and do not hold the same accountability for shaping organizational behavior and removing systemic constraints.

In systems thinking, value of a system passes through its what?

Answer: Interconnections

In systems thinking, value flows through a system via its interconnections — the relationships, links, and flows between components that determine how the system behaves as a whole. Integrations, interactions, and interdependencies are related concepts but are not the precise term used in systems thinking to describe the channels through which value and information pass between system elements.

What can a Release Train Engineer use to support relentless improvement for the Program Increment?

Answer: Inspect and Adapt event

The Inspect and Adapt (I&A) event is the dedicated ART-level ceremony held at the end of each Program Increment for the purpose of relentless improvement. It includes a PI System Demo, quantitative measurement, and a structured problem-solving workshop. An Iteration Retrospective operates at the team level, not the ART level. Release management meetings and Product Owner syncs serve coordination purposes, not systematic PI-level improvement.

Which two behaviors are an important part of the Release Train Engineer role?

Answer: Coach leaders to increase alignment

The RTE serves as a servant leader and coach, so coaching leaders to increase alignment directly reflects the role's purpose — helping leaders across the ART stay coordinated and Lean-Agile in their thinking. Providing answers about Features and analyzing backlogs are Product Owner and Product Management responsibilities. Managing dependencies for teams and driving them to specific outcomes would undermine team autonomy and contradict the servant leadership model the RTE is meant to embody.

The goal of Lean is to deliver the maximum customer value in the shortest sustainable lead time while providing what else?

Answer: The highest possible quality

Lean's goal is explicitly three-part: deliver maximum customer value in the shortest sustainable lead time while providing the highest possible quality. Quality is inseparable from Lean because defects create waste, rework, and delays that undermine both value delivery and speed. A Continuous Delivery Pipeline is a SAFe enabler of that goal, and improved capacity allocation is a means, not an end — neither completes Lean's core definition.

What is the main reason why some teams never reach Stage 4 (Performing) in the stages of high performing teams?

Answer: Because no one guides them

Tuckman's stages — Forming, Storming, Norming, and Performing — describe a natural progression, but teams do not automatically advance through them. Without deliberate guidance from a coach, Scrum Master, or leader who can help the team navigate conflict, build norms, and establish trust, many teams remain stuck in the Norming stage. Conflicts exist in all teams and alone do not prevent progression; what's missing is someone actively facilitating the team's development.

When should a Product Owner (PO) develop preliminary Iteration Goals?

Answer: Prior to iteration planning

The Product Owner must prepare preliminary Iteration Goals before iteration planning begins so the team enters the meeting with a clear sense of direction and priorities. Developing them during PI Planning conflates two distinct events. Developing them after PI Planning is too late, as planning needs this input. Backlog refinement is for clarifying stories, not for establishing the iteration-level goals that frame the planning conversation.

Who can the Release Train Engineer work to help eliminate policies and procedures that demotivate employees?

Answer: Lean-Agile Leaders

Lean-Agile Leaders in SAFe are explicitly accountable for modeling Lean-Agile mindset and behavior and for removing organizational impediments — including demotivating policies and procedures — that prevent teams from performing. Business Owners focus on business value, Portfolio Managers on portfolio strategy, and Product Management on features and roadmaps. None of those roles carry the same organizational authority and accountability for cultural and policy-level change.