Free SP-SAFE-PRACTITIONER Practice Test

Business Owners first assign a preliminary business value (1-10) to each team’s PI Objectives during the Draft Plan Review. This early valuation guides teams in the second breakout session, allowing them to refine scope and align with economic priorities before objectives are finalized.

A. Final plan review presents the updated plan but business value has already been assigned.
B. Team breakout sessions are internal to teams; Business Owners are not present to score value.
C. Management Review involves managers only; no assignment of business value occurs.

1. SAFe 6.0, “PI Planning” article – Step 7: Draft Plan Review, para. 3 (“Business Owners…assign business value to each objective”).

2. SAFe 6.0 Product Manager/Product Owner courseware, Module “PI Objectives,” p. 14 (“Value scoring is done in the draft review to drive re-planning”).

An Agile Release Train (ART) is the primary value delivery construct in SAFe. It operates on a cadence with specific events. The Innovation and Planning (IP) Iteration is a unique, cadence-based timebox for the entire ART. It occurs at the end of every Program Increment (PI) and serves critical purposes, including the Inspect & Adapt (I&A) event, innovation, and infrastructure work. While technically a timebox containing events, it is considered a fundamental part of the ART's rhythm and is often categorized as a major ART-level occurrence.

A. Iteration Review is a team-level event where the Agile Team demonstrates its completed work for the iteration to stakeholders.
C. Team Sync is a brief, recurring meeting for members of an individual Agile Team to coordinate their work, similar to a daily stand-up.
D. Coach Sync is a meeting for Scrum Masters/Team Coaches and the Release Train Engineer (RTE) to coordinate dependencies and resolve impediments, which is a component of the broader ART Sync event.

- Scaled Agile, Inc. (2023). Innovation and Planning Iteration. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/innovation-and-planning-iteration/ (Specifically, the first paragraph describing the IP Iteration as a "key element of the ART's rhythm").

- Scaled Agile, Inc. (2023). ART and Team Events. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/art-and-team-events/ (This article lists the main ART events, and the I&A event occurs during the IP Iteration, linking the two).

The SAFe Portfolio Canvas is the single-page artifact that records the current state of the portfolio (customers, value propositions, solutions, funding, KPIs) and is then analyzed to design the desired future state.

A. Portfolio Vision describes the desired future, not the current state.
B. Portfolio Kanban visualizes epic flow; it does not capture the full current portfolio model.
D. Portfolio Backlog lists approved epics but omits many elements required for a holistic state view.

1. Scaled Agile, Inc. “Portfolio Canvas”, section ‘Details – Purpose’, 2023.

2. Scaled Agile, Inc. “Lean Portfolio Management”, Fig. 4 ‘Canvas informs future state’, 2023.

In SAFe, a Feature is a unit of work that delivers business value and fulfills a stakeholder need. A key characteristic of a Feature is its size. To ensure a continuous flow of value and enable effective planning and execution for an Agile Release Train (ART), Features are defined and sized to be completed within a single Program Increment (PI). If a business need is too large to fit into one PI, it is typically defined as an Epic and broken down into smaller Features.

A. One month is not a standard SAFe timebox for sizing Features; it is shorter than a typical PI.
B. One year is far too long for a Feature; work of this magnitude would be classified as a Portfolio Epic.
C. One Iteration is the timebox for a Story, which is a smaller component of a Feature.

1. Scaled Agile, Inc. (2023). Feature. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/features-and-capabilities/. (See the introductory paragraph, which states, "Features are sized to fit in a Program Increment (PI).").

Lean-Agile leaders focus on breaking down functional silos to organize teams around the flow of value. SAFe Principle #10, "Organize around value," guides leaders to create cross-functional Agile Release Trains (ARTs). These ARTs comprise all the people—business, development, testing, operations, etc.—needed to define, build, test, and release value to the customer. This structure optimizes for the smooth flow of value delivery by fostering collaboration, reducing handoffs, and aligning everyone toward a common set of objectives, rather than optimizing for functional expertise in isolation.

A. The goal is to break down organizational boundaries and silos, not enforce them, to improve the flow of value.
C. The aim is to optimize horizontal communication across the value stream, not just vertical communication within functional hierarchies.
D. The intent is to reduce friction and delays caused by handoffs between teams, thereby improving collaboration and flow.

1. Scaled Agile, Inc. (2023). SAFe Principle #10 – Organize around value. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/organize-around-value/. (This article directly explains the principle of breaking down silos to align everyone needed to deliver value).

2. Scaled Agile, Inc. (2023). Lean-Agile Leadership. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/lean-agile-leadership/. (This competency describes how leaders drive this change, including organizing around value).

SAFe Principle #8, "Unlock the intrinsic motivation of knowledge workers," is heavily influenced by Daniel Pink's work on motivation. It posits that for creative and knowledge-based work, traditional extrinsic motivators (like compensation) are less effective than intrinsic ones. The principle identifies three key elements for fostering intrinsic motivation: autonomy, mastery, and purpose. The question already provides purpose and implies autonomy through "minimum possible constraints." Therefore, autonomy is the explicit missing component required by this principle.

B. Innovation is an outcome of a motivated workforce, not a direct input required to create motivation itself.
C. Incentive-based compensation is an extrinsic motivator, which this principle argues can be counterproductive for knowledge workers.
D. Transparency is a SAFe Core Value, but it is not one of the three primary elements of intrinsic motivation described in Principle #8.

1. Scaled Agile, Inc. (2023). SAFe Principle #8: Unlock the intrinsic motivation of knowledge workers. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/unlock-the-intrinsic-motivation-of-knowledge-workers/. (Refer to the section "Autonomy, Mastery, and Purpose").

2. Pink, D. H. (2009). Drive: The Surprising Truth About What Motivates Us. Riverhead Books. (This book is the foundational source for SAFe Principle #8, outlining Autonomy, Mastery, and Purpose as the pillars of motivation).

SAFe Principle #8, "Unlock the intrinsic motivation of knowledge workers," emphasizes creating an environment of mutual influence. This is achieved by providing autonomy and purpose, minimizing constraints, and decentralizing decision-making. Autonomy gives knowledge workers the freedom to innovate and manage their own work, which is a powerful intrinsic motivator. This approach, supported by research from figures like Daniel Pink, leads to higher levels of engagement and better outcomes than traditional extrinsic reward systems.

A. Pay-for-performance is an extrinsic motivator, which can be counterproductive for creative or cognitive work, potentially reducing intrinsic motivation.
C. Parallel development is a technical strategy for executing work concurrently; it is not a direct factor in psychological motivation.
D. Team performance incentives are extrinsic rewards. While team-based, they still focus on "if-then" compensation rather than intrinsic drivers like purpose or mastery.

Scaled Agile, Inc. (2023). "SAFe Principle #8 - Unlock the intrinsic motivation of knowledge workers". Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/unlock-the-intrinsic-motivation-of-knowledge-workers/. The article states, "Create an environment of mutual influence... Provide autonomy and purpose, minimize constraints..."

Pink, D. H. (2009). Drive: The Surprising Truth About What Motivates Us. This work, cited by SAFe, identifies autonomy, mastery, and purpose as the three pillars of intrinsic motivation for 21st-century work.

The Iteration Retrospective is a dedicated event for the Agile Team to reflect on its process and identify ways to improve its performance. This directly aligns with the SAFe Core Value and Continuous Learning Culture dimension of 'Relentless Improvement.' The primary output of the retrospective is a set of improvement items that the team will action in the next iteration, making the process of continuous enhancement tangible and systematic.

B. Apply systems thinking is a broader SAFe-Lean principle for optimizing the full value stream, not a specific responsibility of the team's internal process retrospective.
C. Take an economic view is a SAFe principle used for decision-making and prioritization, which is more relevant to planning events than process improvement retrospectives.
D. Connect to the customer is the primary focus of the Iteration Review, where the team demonstrates the increment and gets feedback on the product itself.

1. Scaled Agile, Inc. (2023). Iteration Retrospective. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/iteration-retrospective/. (The article states, "The iteration retrospective is a regular event... to reflect on the iteration and identify and agree on improvement actions," directly linking it to the concept of relentless improvement.)

2. Scaled Agile, Inc. (2023). Continuous Learning Culture. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/continuous-learning-culture/. (This article identifies "Relentless Improvement" as a key dimension, of which retrospectives are a core practice.)

SAFe Team Kanban is a method designed for teams whose work is characterized by a continuous flow of tasks and unpredictable arrival rates, such as maintenance or support teams. The scenario describes a team that cannot plan predictably and needs to respond quickly to emerging needs. Kanban helps manage this by visualizing workflow, limiting Work in Process (WIP), and using a flow-based approach rather than time-boxed iterations. The daily meeting aligns with Kanban's practice of daily stand-ups to manage the flow of work for that day.

A. A SAFe Platform Team is a team topology that provides services to other teams; it describes the team's purpose, not its workflow method.
B. A SAFe Enabling Team is a team topology that provides specialized skills or support; it describes the team's function, not its process.
D. SAFe XP (Extreme Programming) is a set of software engineering practices that can be used by any team, but it doesn't specifically address the workflow management of unpredictable work.

1. Scaled Agile, Inc. (2023). Team Kanban. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/team-kanban/. The article states, "Kanban systems are used by teams that are focused on maintenance and support... where priorities can shift on a daily basis."

2. Scaled Agile, Inc. (2023). Agile Teams. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/agile-teams/. This article describes how teams can be organized by topology (stream-aligned, enabling, etc.) and can use different methods like Scrum or Kanban.

The Agile Manifesto outlines four core values that prioritize certain aspects of software development over others. The third value explicitly states, "Customer collaboration over contract negotiation." This emphasizes building a partnership with the customer to create the best product, rather than being constrained by rigid, upfront contractual agreements. The focus is on continuous interaction and adaptation to meet evolving customer needs, which is more effective than relying on a fixed contract.

A. "Ongoing internal conversation" is not the term used in the Manifesto; the contrast is specifically with formal contracts.
C. "A constant indefinite pace" is a misinterpretation of the principle "Agile processes promote sustainable development," not a Manifesto value.
D. Feature negotiation is a part of customer collaboration, not something that collaboration is valued over.

1. Beck, K., et al. (2001). Manifesto for Agile Software Development. AgileManifesto.org. Retrieved from https://agilemanifesto.org/

2. Scaled Agile, Inc. (2023). SAFe Principle #10 - Organize around value. Scaled Agile Framework. Retrieved from https://www.scaledagileframework.com/organize-around-value/ (This article references the Agile Manifesto values as foundational).