Question 1

During which PI Planning activity do Business Owners assign business value to PI Objectives?

Accepted Answer

D

Explanation: 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

Question 2

What is an example of an ART event?

Accepted Answer

B

Explanation: 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

Question 3

What is used to capture the current state of the Portfolio and provide input for defining the future state?

Accepted Answer

C

Explanation: 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

Question 4

According to SAFe, a Feature should be sized to fit into what duration?

Accepted Answer

D

Explanation: = 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

Question 5

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

Accepted Answer

B

Explanation: 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

Question 6

What else does the SAFe principle, "unlock the intrinsic motivation of knowledge workers", require besides purpose and minimum possible constraints?

Accepted Answer

A

Explanation: 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

Question 7

Which factor helps unlock the intrinsic motivation of knowledge workers?

Accepted Answer

B

Explanation: 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 …

Question 8

Which of the following Agile Team responsibilities is associated with the Iteration Retrospective?

Accepted Answer

A

Explanation: = 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

Question 9

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. Which of the following SAFe Lean-Agile methods should Team A use to plan and
execute their work?

Accepted Answer

C

Explanation: 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.

Question 10

Which statement is a value from the Agile Manifesto?

Accepted Answer

B

Explanation: 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

Question 11

Which of the following statements describes the Release Train Engineer role?

Accepted Answer

B

Explanation: The Release Train Engineer (RTE) is a servant leader and coach for the Agile Release Train (ART), which is a group of Agile teams that work together to deliver value. The RTE facilitates the ART events and processes, and supports the teams in delivering value. They communicate with stakeholders, escalate impediments, help manage risk, and drive relentless improvement. The RTE also serves as the ART Chief Coach, which means they help the teams apply and improve the SAFe principles and practices, such as PI planning, system demos, inspect and adapt, and innovation and planning1. The RTE is not the team backlog owner, the ART-level content authority, or the technical leader of the ART, but rather the facilitator and enabler of the ART’s success. Reference: Release Train Engineer - Scaled Agile Framework, Release Train Engineer(RTE): Roles & Responsibilities - KnowledgeHut, Release Train Engineer - Scaled Agile Framework

Question 12

Which of the following SAFe Core Values involves coaching aspiring developers to grow their skillsets and fill new roles throughout the organization?

Accepted Answer

B

Explanation: Respect for People is one of the four SAFe Core Values that guide the behaviors and actions of everyone participating in a SAFe portfolio. Respect for People means that everyone is valued and deserves respect, regardless of their role, background, or experience. It also means that everyone is empowered to contribute, learn, and grow within the organization. Respect for People involves coaching aspiring developers to grow their skillsets and fill new roles throughout the organization, as well as providing them with opportunities for feedback, recognition, and career development. Respect for People also fosters a culture of trust, collaboration, and psychological safety, where people can express their ideas, opinions, and concerns without fear of judgment or retaliation. Reference: Core Values - Scaled Agile Framework, Respect for People - Scaled Agile Framework

Question 13

A SAFe Portfolio is a collection of what?

Accepted Answer

A

Explanation: According to SAFe, a SAFe Portfolio is a set of value streams that delivers a continuous flow of valuable solutions to customers within a common funding and governance model. A SAFe portfolio aligns strategy to execution via a collection of Development Value Streams (DVS). Each DVS develops one or more Solutions necessary for the portfolio to accomplish its business mission and vision, operating under a shared governance model1. A DVS is a long-lived series of steps that an organization uses to deliver value to a customer or stakeholder2. A DVS can be internal or external, and it can span multiple ARTs and suppliers3. A DVS is not the same as a functional team, a solution, or a business unit, which are different ways of organizing work, products, or organizational structures. Reference: Portfolio - Scaled Agile Framework, Development Value Stream - Scaled Agile Framework, Value Stream - Scaled Agile Framework.

Question 14

Iteration planning, Iteration review, and backlog refinement are examples of which type of event

Accepted Answer

B

Explanation: Iteration planning, Iteration review, and backlog refinement are examples of team events, which are events that occur within the Agile team to plan, execute, and improve their work. Team events are aligned with the Iteration cadence, which is typically two weeks. Team events include: Iteration planning: A meeting where the team reviews the team backlog, estimates the stories, and commits to the Iteration goals Daily stand-up: A 15-minute meeting where the team members synchronize their work, share their progress, and identify any impediments or dependencies Backlog refinement: An ongoing activity where the team and the Product Owner collaborate to refine the team backlog, split features into stories, write acceptance criteria, and prioritize the work Iteration review: A meeting where the team demonstrates the completed stories to the Product Owner and other stakeholders, and collects feedback and validation Iteration retrospective: A meeting where the team reflects on their performance, identifies what went well and what can be improved, and agrees on action items to implement in the next Iteration Team events are different from PI events, which are events that occur at the program level and involve all the teams and stakeholders of an Agile Release Train (ART). PI events include: PI planning: A two-day event where the ART aligns on a common vision, mission, and goals for the upcoming Program Increment (PI), and creates a plan for delivering value System demo: A meeting where the ART demonstrates the integrated solution to the Business Owners and other stakeholders, and collects feedback and validation Inspect and Adapt (I&A): A one-day event where the ART reviews the PI results, identifies the strengths and weaknesses, and creates an improvement backlog for the next PI Team events are also different from sync events, which are events that occur at the large solution level and involve multiple ARTs and Solution Trains that are working on a complex solution. Sync events include: Solution demo: A meeting where the Solution Train demonstrates the integrated solution to the Customers and other stakeholders, and collects feedback and validation Pre- and Post-PI planning: Meetings where the Solution Train aligns on a common vision, mission, and goals for the upcoming PI, and coordinates the dependencies and risks across the ARTs Solution I&A: A meeting where the Solution Train reviews the PI results, identifies the strengths and weaknesses, and creates an improvement backlog for the next PI Team events are also different from program events, which are events that occur at the portfolio level and involve the Portfolio Management and other strategic roles. Program events include: Portfolio sync: A meeting where the Portfolio Management reviews the portfolio vision, strategy, and roadmap, and aligns the value streams and ARTs on the portfolio priorities and objectives Lean budget guardrails: A set of policies and guidelines that govern the allocation and spending of the portfolio budget across the value streams and ARTs Portfolio Kanban: A system that visualizes and manages the portfolio work items, such as epics and capabilities, and ensures that they are aligned with the portfolio strategy and value delivery Reference: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Team Events, PI Events, Sync Events, [Program Events]

Question 15

What is one benefit of Story acceptance criteria?

Accepted Answer

D

Explanation: One benefit of Story acceptance criteria is to provide Story details from a testing point of view. Acceptance criteria are the conditions or rules that a user story must meet to be considered complete and acceptable by the customer or stakeholder. They define the scope and boundaries of the user story and help the team to understand what needs to be done and how to test it. Acceptance criteria also facilitate communication and collaboration between the team and the customer or stakeholder, as they provide a common language and a shared understanding of the expected outcome. Reference: What is User Story and Acceptance Criteria (Examples), Acceptance Criteria: Everything You Need to Know Plus Examples

Free Scaled Agile SP-SAFe-Practitioner Actual Exam Questions