SP-SAFE-PRACTITIONER Practice Questions

During the draft plan review, the teams present their draft PI objectives and plans to the other

teams and the Business Owners. The Business Owners then assign a business value to each PI

objective, based on the conversation with the team and the alignment with the vision and goals. The

business value is a number between 1 (lowest) and 10 (highest) that reflects the relative importance

and expected benefit of the objective. The business value is used to measure the ART’s predictability

and performance at the end of the PI. Reference: PI Objectives, PI Planning, Your Guide to Writing

Great Iteration and PI Objectives

An ART event is a meeting or ceremony that involves all the teams in an Agile Release Train (ART)

and helps them align, collaborate, and deliver value. An example of an ART event is the Innovation

and Planning (IP) Iteration, which is a two-week period at the end of each Program Increment (PI)

that provides time for innovation, planning, and improvement activities. During the IP Iteration,

teams can explore new ideas, work on technical debt, conduct hackathons, prepare for the next PI

Planning, and conduct the Inspect and Adapt workshop. Reference: Agile Release Train, Scaled Agile:

ART Events Overview, Innovation and Planning Iteration

The Portfolio Canvas is a tool that defines the current state of the portfolio, as well as the future

state vision, using the Business Model Canvas template1. It describes the development value

streams, the solutions they deliver, the customers they serve, the budget allocated to each value

stream, and other vital activities and events required to achieve the portfolio vision2. The Portfolio

Canvas is used to capture and analyze the current state of the portfolio, as well as to generate and

evaluate multiple future state scenarios, based on the SWOT and TOWS analysis2. The Portfolio

Canvas provides input for defining the future state vision and the portfolio

backlog2. Reference: Business Model Canvas, Portfolio Vision

= According to SAFe, a Feature should be sized to fit into one Program Increment (PI), which is a

timebox of 8 to 12 weeks, typically consisting of 4 to 6 iterations1. A Feature is a service provided by

the system that fulfills some important stakeholder needs and delivers business value2. A Feature

should be small enough to be completed by a single Agile Release Train (ART) within a PI, but large

enough to provide significant and measurable value3. A Feature should also be testable,

demonstrable, and deployable4. Reference: = 1: Program Increment - Scaled Agile Framework; 2:

Features and Capabilities - Scaled Agile Framework; 3: Right-Sizing Features for SAFe Program

Increments - Scaled Agile Framework; 4: Feature - Scaled Agile Framework

Lean-Agile leaders try to connect the silos of business, software, test, and quality assurance to

create a culture of collaboration and shared responsibility across the value stream. By breaking down

the barriers between different functions, Lean-Agile leaders enable faster feedback, shorter lead

times, higher quality, and better customer satisfaction. Connecting the silos also helps to align the

teams around a common vision, mission, and goals, and to foster a Lean-Agile mindset that

embraces change and innovation. Reference: SAFe Core Values, Agile Practice Exam Flashcards, SAFe

4.6 exam prep - Improved - extended Flashcards, Stop Breaking Down Silos and Start Connecting

Them

According to the SAFe principle, “unlock the intrinsic motivation of knowledge workers”, knowledge

workers need autonomy, mastery, and purpose to be motivated and creative. Autonomy means

giving them the freedom to choose how to do their work, without micromanagement or excessive

control. Mastery means providing them with opportunities to learn new skills and improve their

craft. Purpose means aligning their work with a meaningful and inspiring vision. These three factors

foster intrinsic motivation, which is the drive to perform an activity without any obvious external

rewards. Reference: Principle #8 - Unlock the Intrinsic Motivation of Knowledge Workers - Scaled

Agile Framework, Principle #8 - Unlock the Intrinsic Motivation of Knowledge Workers - Scaled Agile

Framework

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, the factor

that helps unlock the intrinsic motivation of knowledge workers is autonomy. Autonomy means

giving knowledge workers the freedom and responsibility to make decisions about their work, such

as what to work on, how to do it, and when to do it. Autonomy fosters creativity, innovation, and

engagement, as knowledge workers can pursue their own interests and passions, and feel a sense of

ownership and accountability for their outcomes. Autonomy also supports the Agile principle of self-

organizing teams, which are more productive and responsive to change than traditional, command-

and-control teams. Reference: Principle #8 - Unlock the Intrinsic Motivation of Knowledge Workers -

Scaled Agile Framework, Which factor helps unlock the intrinsic motivation of knowledge

workers?, Principle #8: Unlock the intrinsic motivation of knowledge workers …

= The Agile Team responsibility that is associated with the Iteration Retrospective is “Improve

relentlessly”. This responsibility reflects the SAFe Core Value of Relentless Improvement, which

means that the team continuously reflects on their practices, identifies improvement opportunities,

and implements them in the next iteration. The Iteration Retrospective is a regular event where the

team members discuss the results of the iteration, review their practices, and identify ways to

improve. The team uses various techniques to collect feedback, perform root cause analysis, and

prioritize improvement actions. The improvement actions are added to the Team Backlog and

reviewed in the next Iteration Planning event. Reference: = Relentless Improvement - Scaled Agile

Framework, Iteration Retrospective - Scaled Agile Framework1

SAFe Team Kanban is a method that enables teams to manage their flow of work using a visual

board and a set of policies. It is especially suitable for teams that have unpredictable or interrupt-

driven work, such as maintenance, support, or operations teams1. SAFe Team Kanban helps teams to

visualize their work, limit their work in progress (WIP), measure and improve their flow, and

implement feedback loops2. Team A is a maintenance team that cannot always predictably plan their

work. They like to meet daily to review the needs of the system and plan for how they can quickly

address those needs during the workday. Therefore, SAFe Team Kanban is the most appropriate SAFe

Lean-Agile method for Team A to plan and execute their work. Reference: Team Kanban - Scaled Agile

Framework, SAFe Lean-Agile Principles - Scaled Agile Framework

SAFe Team Kanban is a method that helps teams facilitate the flow of value by visualizing workflow,

establishing Work In Process (WIP) limits, measuring throughput, and continuously improving their

process1. It is suitable for teams that have a rapid and uneven arrival of work and fast-changing

priorities, such as maintenance teams2. The other options are not appropriate for Team A’s

context. SAFe Platform Team is organized around developing and supporting platforms that provide

services to other teams3. SAFe Enabling Team is organized to assist other groups with specialized

capabilities and help them become proficient in new technologies4. SAFe XP Team is an Agile Team

method that combines the power of Scrum with Extreme Programming (XP) practices and operates

within the ART iteration cadence5.

The Agile Manifesto is a set of values and principles that guide the software development process.

One of the values is “responding to change over following a plan”. This means that the team values

the customer’s needs and feedback over the plan and process. The team embraces change as an

opportunity to deliver better solutions and adapts to changing requirements and

priorities. Reference: The 4 Values and 12 Principles of the Agile Manifesto - Smartsheet, 12

Principles Behind the Agile Manifesto | Agile Alliance