Pass the Scaled Agile SAFe Practice Consultant SAFe-SPC Questions and answers with ExamsMirror

SAFe recommends organizing ARTs around value and end-to-end functionality, not geography or cost centers. Two distributed ARTs—each cross-functional and capable of delivering end-to-end value—enables global collaboration while preserving Agile principles.

“ARTs should be formed around delivering end-to-end value, even when teams are distributed globally. Organizing by function or geography creates silos and dependencies, undermining flow and agility.”

(Source: SAFe 6.0 Framework: ART Organization; SPC 6.0 Guide, “Designing the Implementation”)

===========

The Architectural Runway in SAFe consists of the existing code, components, and technical infrastructure necessary to support the implementation of prioritized, near-term Features without excessive redesign and delay. Its importance is twofold:

It supports a stable velocity (A): Teams need sufficient architectural runway to maintain a predictable velocity and reduce technical debt. As stated in SAFe, “Architectural Runway enables teams to build features quickly and efficiently, thus maintaining stable velocity.”

It iteratively evolves the architecture to meet changing needs (C): SAFe recommends an incremental and emergent architectural approach. The runway is not static; it evolves to meet the emerging business and technical requirements, “just enough, just in time.”

Incorrect options:

B is incorrect—while documentation may be produced, the runway itself is not documentation but actual working infrastructure.

D is incorrect—runway specifically supports technical changes, not nontechnical ones.

In SAFe, Product Management is responsible for defining and communicating the Vision for the Agile Release Train (ART) and each Program Increment (PI).

The Vision describes the current and future state of the solution and helps align all teams in the ART towards the same objectives. Product Owners support and refine this vision but do not own it.

The three primary outputs of PI Planning are:

Program Board (A): Visualizes Features, dependencies, and delivery milestones across teams.

Team PI Objectives (B): Clear, measurable commitments from each team.

Vote of confidence/commitment (D): ART-wide commitment to the PI plan.

“Top 10 Features,” “Portfolio Vision,” and “Iteration Goals” are not standard outputs of the PI Planning event.

“The key PI Planning outputs are the Program Board, Team PI Objectives, and a collective confidence vote/commitment.”

(Source: SAFe 6.0 Framework: PI Planning Outputs; SPC 6.0 Guide “Launching an Agile Release Train”)

SAFe, referencing Daniel Pink’s “Drive,” identifies that making a contribution (B) and autonomy (E) are major factors in unlocking intrinsic motivation for knowledge workers. External motivators (like incentives, rankings, or strict MBOs) are less effective for knowledge work.

“Knowledge workers are most motivated by autonomy, purpose (making a contribution), and mastery, rather than extrinsic rewards.”

(Source: SAFe 6.0 Framework: Principle #8 – Unlock the intrinsic motivation of knowledge workers.)

The System Demo is a key event in SAFe that happens at the end of every iteration. It provides an integrated view of the new features delivered by all the teams in the Agile Release Train during the most recent iteration. This demonstration allows stakeholders to evaluate the solution’s progress and provide feedback.

During PI Planning, ROAMing risks (A) and assignment of business value to objectives (B) happen on Day 2. Day 1 is primarily focused on context-setting, team breakouts, and plan creation, while Day 2 includes management review, risk ROAMing, and business value assignment to PI Objectives.

“On Day 2 of PI Planning, teams assign business value to objectives and ROAM risks. Day 1 is for context and planning.”

(Source: SAFe 6.0 Framework: PI Planning; SPC 6.0 Guide “Launching an Agile Release Train”)

===========

SAFe recommends a Program Predictability Measure target of 80–100%. This range is considered healthy for Agile Release Trains, demonstrating that teams are reliably delivering on their committed PI Objectives while still allowing for adaptation and innovation.

SAFe adopts the five primary economic factors from Don Reinertsen’s “The Principles of Product Development Flow.” These are:

Development expense,

Lead time,

Product cost,

Value,

Risk.

From the options given:

A. Lead time is correct (one of the primary factors).

C. Return on Investment (ROI) is a direct measurement of value, so this aligns with “Value.”

E. Development expense is correct.

“Value stream budget” is not one of the original economic factors. “Risk” is a primary factor, so if you need only three, the best answers are A, C, and E.

When the ART cannot show integrated value at the System Demo, it indicates that teams are not continuously integrating and testing, leading to lack of transparency and feedback. SAFe emphasizes continuous integration and working, tested systems at every iteration. The best immediate action is to stop new work and focus on integrating and testing what has been built, learning from this to improve future practices. This will help restore trust with stakeholders and reveal root causes for future improvements.

“When the system is not integrated, the team should stop developing new functionality and invest in integration and testing. This enables learning, ensures stakeholder visibility, and helps restore the regular cadence of System Demos.”

(Source: SAFe 6.0 Framework: System Demo, Continuous Integration; SPC 6.0 Guide, “Coaching ART Execution”)

===========