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

SAFe and Kanban both define classes of service as ways to handle work items based on urgency and business need. The typical Kanban classes of service are:

Fixed date (B): Items that must be completed by a specific deadline.

Expedite (C): Items that need to be done as soon as possible, jumping the queue.

Standard (D): Normal priority work items.

“Funnel,” “Accepted,” and “Review” are not classes of service; they refer to states or workflow stages.

“Typical Kanban classes of service for Agile teams include Standard, Fixed Date, and Expedite.”

(Source: SAFe 6.0 Framework: Team Kanban; SPC 6.0 Guide, “Building Solutions with Agile Product Delivery”)

SAFe recommends feature branching only when necessary and encourages frequent integration to avoid the overhead and risk associated with long-lived branches. “Continuously synchronize all Feature and team branches” implies maintaining multiple long-lived branches, which is contrary to SAFe’s DevOps and continuous integration best practices.

“Minimize branching and integrate frequently. Long-lived branches and excessive synchronization are discouraged as they increase complexity and risk.”

(Source: SAFe 6.0 Framework: DevOps; SPC 6.0 Guide “Building Solutions with Agile Product Delivery”)

===========

Long queues in product development systems create multiple problems:

Higher variability (A): Work spends more time waiting, which increases variability in lead times.

More multitasking (D): With many items in process, people switch between tasks, reducing effectiveness.

Slower delivery (E): The more work in the queue, the longer it takes to get through the system.

Lower quality (F): Long waits cause context loss, handoff errors, and rework, reducing quality.

“Long queues increase cycle times and variability, cause more multitasking, slow delivery, and lower quality.”

(Source: SAFe 6.0 Framework: Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths.)

===========

The Solution Context defines the environment in which the solution operates, including operational, regulatory, deployment, and support conditions. For a Solution Architect, understanding this environment is essential to ensure the solution will function as required in its real-world context.

In SAFe 6.0,Capabilitiesare defined as "higher-level solution behaviors that typically span multiple ARTs." They are maintained in theSolution Train Backlogand are sized and split into Features for implementation by individual ARTs. The SAFe 6.0 guidance specifically states:

“Capabilities are larger solution behaviors that often span multiple Agile Release Trains. They are typically sized to be delivered in a Planning Interval (PI) and are broken down into Features to facilitate implementation.”

This distinguishes Capabilities from Epics and Features. Unlike Epics, which require Lean Business Cases and approval through Portfolio Kanban, Capabilities follow a breakdown path to Features for execution. Therefore,they are a level above Features, not a synonym for Epics or Features.

Lowering WIP limits reduces multitasking, exposes bottlenecks, and encourages team members to collaborate to finish work before starting new work. This is a core Lean and SAFe principle to increase flow and throughput.

A is incorrect; excessive WIP delays feedback. B is incorrect; WIP is highly related to utilization and flow.

Deploying to a production-equivalent staging environment enables teams to validate both new functionality and Nonfunctional Requirements (NFRs) in an environment that matches production. This mitigates risk, uncovers issues early, and ensures that what works in staging will likely work in production.

“Deploying increments to a production-equivalent staging environment ensures compatibility and readiness of both functionality and NFRs before moving to production.”

(Source: SAFe 6.0 Framework: DevOps and Continuous Delivery; SPC 6.0 Guide “Building Solutions with Agile Product Delivery”)

===========

Limiting WIP:

Reduces multiplexing (A): Teams and individuals do less context switching and focus more.

Decreases wait times (B): Items flow through the system faster with less time spent waiting.

Increases throughput (E): Limiting WIP ensures more items complete in a given period.

“Limiting WIP decreases wait times, reduces context switching (multiplexing), and increases throughput.”

(Source: SAFe 6.0 Framework: Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths.)

===========

The System Team in SAFe is a specialized Agile team that supports the ART by providing system-level integration, testing, and deployment infrastructure. Their primary responsibilities include:

End-to-end system testing (C)

Building and maintaining a production-equivalent staging environment (D)

Deploying to staging (E)

Defining Solution architecture (A) is the responsibility of Solution/System Architects. Creating new automated test scenarios (B) is typically a responsibility of the Agile Teams themselves.

“The System Team assists in building and maintaining development, test, and staging environments, performing end-to-end system integration and testing, and deploying to these environments.”

(Source: SAFe 6.0 Framework: System Team; SPC 6.0 Guide “Building Solutions with Agile Product Delivery”)

===========

SAFe best practice is to split large Epics into Features that fit within a PI and then use capacity allocation to ensure the right balance between new business Features and Enabler work. Capacity allocation is a specific SAFe tool to guide what goes into the PI, especially when dealing with both Features and Epics.