Agile Release Train (ART) Flashcards

What is an Agile Release Train (ART) in SAFe?

Answer: A fixed group of Agile teams that plan, commit, and execute together on a shared mission

An ART is a long-lived team of Agile teams that plans, commits, and executes together to deliver value continuously in Program Increments.

How many people typically make up an Agile Release Train?

Answer: 50–125 people

SAFe defines an ART as consisting of 50–125 people, typically 5–12 Agile teams plus shared services and supporting roles.

What is the typical duration of a Program Increment (PI) in SAFe?

Answer: 8–12 weeks

A PI typically lasts 8–12 weeks and consists of 4–5 development iterations plus one Innovation and Planning (IP) iteration.

Who serves as the servant leader and chief Scrum Master for the Agile Release Train?

Answer: Release Train Engineer (RTE)

The Release Train Engineer (RTE) is the servant leader and chief Scrum Master for the ART, facilitating ART events and coaching teams and leaders.

What is the primary purpose of the Innovation and Planning (IP) Iteration in SAFe?

Answer: To provide a buffer for PI planning, innovation, education, and continuous improvement

The IP Iteration provides dedicated time for PI planning, hackathons, innovation, education, and team improvement activities that enable sustainable pace.

What does the System Demo at the end of each iteration showcase?

Answer: The integrated work of all ART teams for the current iteration

The System Demo shows the current state of the integrated solution built by all teams in the ART, giving stakeholders visibility into working software.

What is the primary purpose of PI Planning in SAFe?

Answer: To align all ART teams to a shared mission and create common PI Objectives with dependencies identified

PI Planning brings the entire ART together to align on a shared mission, identify cross-team dependencies, and produce PI Objectives everyone commits to.

What are PI Objectives in SAFe?

Answer: Business and technical goals the ART commits to achieving during a Program Increment

PI Objectives summarize the business and technical goals that each Agile team and the ART agree to accomplish during a Program Increment.

What is the purpose of the Program Board created during PI Planning?

Answer: A visual display mapping team objectives, features, milestones, and cross-team dependencies across iterations

The Program Board is a visual aid that maps features to iterations across all teams, highlights cross-team dependencies, and identifies key milestones for the PI.

What is an Architectural Runway in SAFe?

Answer: Existing code, components, and infrastructure that support near-term business features without requiring additional enabler work

The Architectural Runway consists of existing technical foundations that allow business features to be implemented without significant delays waiting for architectural work.

How does an ART measure its predictability in SAFe?

Answer: By measuring the ratio of planned business value to actual business value delivered at the PI System Demo

ART predictability is measured by Business Owners comparing planned business value scores set during PI Planning against the actual scores assigned at the PI System Demo.

What is the role of Business Owners in the Agile Release Train?

Answer: Providing business context, validating PI Objectives, and assigning business value scores to team objectives

Business Owners are key stakeholders who validate PI Objectives during PI Planning, assign business value scores, and actively participate in PI reviews and demos.

What happens during the Inspect and Adapt (I&A) event at the end of a PI?

Answer: The ART reviews PI results, holds a quantitative and qualitative retrospective, and runs a problem-solving workshop

The I&A event includes a PI System Demo, a retrospective, and a structured problem-solving workshop to generate improvement stories committed to in the next PI.

What is a 'Feature' in the SAFe Program Backlog?

Answer: A service or function that delivers business value to stakeholders and is sized to be completed within a single PI

A Feature is a unit of value that delivers a service or function to fulfill stakeholder needs and is sized appropriately to be implemented within a single Program Increment.

What is the purpose of Pre-PI Planning in SAFe?

Answer: To prepare leadership, Product Management, and System Architects with a clear vision and prioritized features for the upcoming PI

Pre-PI Planning prepares ART leadership and Product Management to enter PI Planning with a clear vision, prioritized features, and identified constraints or dependencies.

What are 'Uncommitted Objectives' in the context of PI Planning?

Answer: Stretch goals the team will pursue if capacity allows, not part of their firm commitment

Uncommitted Objectives are stretch goals teams accept with the understanding they will pursue them only if committed objectives are completed and capacity remains.

What is the primary responsibility of the Product Manager in the ART?

Answer: Defining and prioritizing the Program Backlog and holding content authority for what the ART builds

The Product Manager owns the Program Backlog, defines and prioritizes Features, and ensures the ART is building the right things by maintaining close contact with customers and stakeholders.

How does SAFe's Continuous Delivery Pipeline (CDP) relate to the ART?

Answer: The CDP is a set of workflows and tools the ART uses to flow value continuously from ideation to on-demand release

The Continuous Delivery Pipeline describes the workflows, activities, and automation that enable the ART to continuously explore, integrate, deploy, and release value on demand.

What is the purpose of the ART Sync in SAFe?

Answer: A regular event where ART leadership and Scrum Masters coordinate, identify impediments, and manage cross-team dependencies

The ART Sync is a regular ceremony where the RTE, Scrum Masters, and key stakeholders align across teams, resolve impediments, and manage inter-team dependencies.

In SAFe, what is a 'Spike' used for?

Answer: A time-boxed research or exploration activity used to gain knowledge and reduce uncertainty

A Spike is a time-boxed investigation or prototype activity teams use to gather information needed to estimate or implement a future story, feature, or technical solution.