Free Scaled Agile SAFe Practice Consultant SPC (6.0) SAFe-SPC Exam Questions

The ROAM (Resolved, Owned, Accepted, Mitigated) technique is used to categorize and address PI risks during the final plan review at PI Planning. Teams and stakeholders collaboratively ROAM the identified risks to ensure alignment and transparency before the confidence vote.

SAFe 6.0, ''PI Planning'' (ROAM Risks in Final Plan Review)

SPC 6.0 Guide, ''Launching an Agile Release Train''

SAFe promotes continuous delivery and recommends releasing products and solutions whenever they meet both business (market) and governance criteria, regardless of iteration or PI boundaries. This enables faster value delivery and more frequent feedback from customers.

''The best time to release is whenever the solution meets market opportunity and governance requirements, not necessarily at PI or iteration boundaries.''

(Source: SAFe 6.0 Framework: Release on Demand; SPC 6.0 Guide, ''Building Solutions with Agile Product Delivery'')

The Agile Manifesto lists four core values and twelve principles. The four values are:

Individuals and interactions over processes and tools,

Working software over comprehensive documentation,

Customer collaboration over contract negotiation,

Responding to change over following a plan.

The principles include statements such as ''Working software is the primary measure of progress,'' ''Business people and developers must work together daily throughout the project,'' and ''Continuous attention to technical excellence and good design enhances agility.''

However, the statement ''Good architectures are built up front so that teams can focus on development'' is NOT a value or principle of the Agile Manifesto. In fact, the Agile approach favors emergent design and evolving architecture, not up-front, fixed architecture. Therefore, option D is NOT part of the Agile Manifesto.

Agile Manifesto (agilemanifesto.org)

SAFe 6.0 SPC Guide: ''Becoming a Lean-Agile Leader'' module

A Lean-Agile Center of Excellence (LACE) is called out by SAFe as one of the primary enablers of a successful SAFe implementation. The LACE is a cross-functional team that drives and sustains the Lean-Agile transformation by providing guidance, training, and support throughout the journey.

SAFe 6.0, ''Create the Implementation Plan'' and ''Establish a LACE''

SPC 6.0 Guide, ''Leading the Change'' and ''Implementing SAFe''

When identifying Value Streams, SAFe recommends looking at how value flows to the customer. This typically means analyzing:

The internal departments which are supported (B): Understanding which departments contribute to the delivery of value helps map operational and development value streams.

The current products which the company sells (D): Products are often a clear indicator of value delivery. Mapping products helps trace value from concept to customer.

Options A and C are not primary criteria for identifying value streams. Project cost accounting (A) is financial and administrative, and number of ARTs (C) is a result of value stream identification, not an input.

SAFe 6.0 Website: Identify Value Streams and ARTs

SPC 6.0 Guide: ''Look for existing products, solutions, and services delivered to the customer, and the people, systems, and steps involved in their flow of value.''

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'')

The ROAM technique (Resolved, Owned, Accepted, Mitigated) is used during Planning Interval (PI) Planning to manage and categorize ART PI Risks. In the PI Planning session, all identified risks are discussed and then categorized using the ROAM framework, which helps teams and stakeholders clarify ownership, mitigation strategies, and acceptance of each risk. According to the SAFe 6.0 official guidance:

'During PI Planning, teams identify program risks and then use the ROAM technique to classify each risk as Resolved, Owned, Accepted, or Mitigated. This collaborative activity ensures transparency and allows teams to address significant risks before proceeding.'

This activity does not take place during backlog refinement, ART syncs, or general team management; it is specific to the PI Planning event.

SAFe 6.0 Website: PI Planning and ROAM

SAFe Practice Consultant SPC (6.0) Training Guide --- 'Launching an Agile Release Train' Module

New Terminology: 'Program PI Risks' are now referred to as 'ART PI Risks'

SAFe recommends the Lean Startup cycle for managing Epics. This process accelerates learning, guides hypothesis-driven development, and reduces risk by enabling incremental evaluation and fast feedback before full investment in new business ideas.

SAFe 6.0, ''Epic'' and ''Lean Startup Cycle'' articles

SPC 6.0 Guide, ''Building Solutions with Agile Product Delivery''

SAFe and Lean-Agile principles recognize that traditional phase-gate milestones (sign-offs at project checkpoints) do not accurately predict or ensure performance or outcomes. Empirical milestones---based on actual, working systems---are favored.

''Phase-gate milestones are not good predictors of progress or project performance; Lean-Agile development relies on objective evaluation of working systems.''

(Source: SAFe 6.0 Framework: Lean-Agile Milestones)

A well-written Objective in the context of OKRs should be inspirational. It should motivate and challenge the team or organization while providing a clear direction. Inspirational Objectives help ensure buy-in and alignment, making them a key quality according to SAFe guidance on OKRs.

SAFe 6.0, ''Objectives and Key Results (OKRs)'' article

SPC 6.0 Guide, ''Accelerating to Business Agility''

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.

SAFe 6.0 Framework: Economic Decision Making

Don Reinertsen, ''The Principles of Product Development Flow''

SAFe 6.0 SPC Guide: ''Exploring Lean Portfolio Management'' module

''Visualize work'' is specifically called out as a practice that supports the SAFe Core Value of Transparency. Making work visible allows teams, ARTs, and stakeholders to see progress, manage flow, and surface issues early, all of which build trust and foster a culture of openness.

SAFe 6.0, ''Core Values'' (Transparency)

SPC 6.0 Guide, ''Thriving in the Digital Age and Business Agility''

Facilitating Value Stream mapping is a direct activity for coaching flow. Value Stream mapping helps teams and organizations visualize and understand their current process, identify bottlenecks, and find opportunities to improve flow and reduce waste, which is a key Lean practice advocated by SAFe.

SAFe 6.0, ''Accelerating Flow'' and ''Value Stream Mapping'' articles

SPC 6.0 Guide, ''Accelerating to Business Agility''

The Quickstart approach for launching an ART is recommended in SAFe because it ''engages all teams in the ART simultaneously, allowing for a fast start and aligning everyone with purpose and intent.'' The Quickstart focuses everyone all at once, drives collective ownership, and increases engagement, which is cited as its main benefit.

SAFe 6.0, ''ART Quickstart'' guidance

SPC 6.0 Study Guide, ''Launching an Agile Release Train''

SAFe creates a second operating system---alongside the existing hierarchical structure---by establishing a value stream network that focuses on customers, products, innovation, and growth. This enables organizations to respond quickly to opportunities without dismantling their existing structure, supporting true business agility.

SAFe 6.0, ''SAFe as a Dual Operating System'' and ''Business Agility'' articles

SPC 6.0 Guide, ''Thriving in the Digital Age and Business Agility''