SP-SAFe-Practitioner Pre-Exam Practice Tests | (Updated 270 Questions)
Valid SP-SAFe-Practitioner Exam Q&A PDF - One Year Free Update
Scaled Agile SP-SAFe-Practitioner Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 111
Which statement describes the information within a Story?
- A. A Story provides just enough information for the intent to be understood by both business and technical people
- B. A Story is written in full detailed specifications so that the work is ready to be implemented immediately
- C. No further conversation is required after the Story is identified because it contains all necessary details
- D. Story acceptance criteria must be finalized before beginning Iteration Planning
Answer: A
Explanation:
Explanation
A Story is a short description of a small piece of desired functionality written from the user's perspective and in their language. A Story has three primary components: Card, Conversation, and Confirmation. The Card captures the essence of the Story using the format: "As a (who), I want (what), so that (why)." The Conversation is the ongoing dialogue between the team and the customer or product owner to elaborate and refine the Story details. The Confirmation is the set of acceptance criteria and tests that verify the Story is done and meets the customer's expectations. A Story provides just enough information for both business and technical people to understand the intent, but not so much that it becomes a specification or a contract. Details are deferred until the Story is ready to be implemented, which allows for more flexibility and feedback. A Story is not a static artifact, but a dynamic one that evolves through collaboration and learning12. References: Story - Scaled Agile Framework, [What is User Story? -
NEW QUESTION # 112
What is an example of a program event?
- A. Innovation and Planning
- B. Iteration review
- C. Scrum of scrums
- D. Daily stand-up
Answer: C
NEW QUESTION # 113
What are the three parts of Inspect and Adapt?
- A. Backlog refinement, qualitative and quantitative measurement, and ROAMing risks
- B. The PI System Demo, confidence vote, and ROAMing risks
- C. The PI System Demo, qualitative and quantitative measurement, and Problem-solving workshop
- D. Backlog refinement, confidence vote, and Problem-Solving workshop
Answer: C
Explanation:
Explanation
The Inspect and Adapt (I&A) is a significant event held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated by the train. Teams then reflect and identify improvement backlog items via a structured, problem-solving workshop. The I&A event consists of three parts: the PI System Demo, where the features developed during the PI are shown and feedback is collected; the quantitative and qualitative measurement, where the teams assess their performance and progress using various metrics and surveys; and the retrospective and problem-solving workshop, where the teams identify and analyze the root causes of their most critical issues and devise action plans to address them12. References: Inspect and Adapt, Exam Study Guide: SP (6.0) - SAFe Practitioner
NEW QUESTION # 114
Team B has elected to stop holding retrospective events so they can spend more time completing Stories.
Which of the following Agile Team responsibilities is Team B over-prioritizing?
- A. Applying systems thinking
- B. Deliver value
- C. Connect with the customer
- D. Plan the work
Answer: B
Explanation:
Explanation
= Deliver value is one of the six Agile Team responsibilities in SAFe, along with aligning to a common mission, applying systems thinking, building incrementally with fast feedback, collaborating and making decisions together, and improving relentlessly. While delivering value is essential for Agile Teams, it should not come at the expense of other responsibilities, especially improving relentlessly. By skipping the retrospective events, Team B is missing an opportunity to reflect on their practices, identify what is working well and what is not, and plan actions to improve their performance and quality. Retrospectives are a key mechanism for implementing the SAFe Core Value of Relentless Improvement and the SAFe Principle #12 - Assume variability; preserve options. References: = Agile Teams - Scaled Agile Framework, Core Values - Scaled Agile Framework, SAFe Principles - Scaled Agile Framework, Exam Study Guide: SP (6.0) - SAFe Practitioner
NEW QUESTION # 115
Which of the following roles is responsible for prioritizing the Agile Team Backlog?
- A. Release Train Engineer
- B. Product Owner
- C. Release Manager
- D. Scrum Master/ Team Coach
Answer: B
Explanation:
Explanation
According to SAFe, the Product Owner (PO) is the member of the Agile Team who serves as the customer proxy and is responsible for working with Product Management and other stakeholders to define and prioritize stories in the Team Backlog1. The PO has the primary role of ensuring that the team delivers value to the business and aligns with the Program Backlog2. The PO collaborates with the team, the Scrum Master/Team Coach, and other stakeholders to refine, order, and maintain the Team Backlog3. The PO also participates in PI Planning, Iteration Planning, System Demo, and Inspect and Adapt events4. References: Product Owner - Scaled Agile Framework, Team Backlog - Scaled Agile Framework, SAFe for Teams - Know Your Role on an Agile Team | Scaled Agile, Exam Study Guide: SP (6.0) - SAFe Practitioner - scaledagile.com.
NEW QUESTION # 116
What is one of the Agile Release Train events?
- A. Iteration Retrospective
- B. Backlog refinement
- C. Product Owner sync
- D. Solution Demo
Answer: D
Explanation:
Explanation
A Solution Demo is one of the Agile Release Train events. A Solution Demo is a periodic event where the current state of the Solution is evaluated by the relevant stakeholders, including customers and users. The Solution Demo provides an opportunity to inspect and adapt the Solution, and to validate that it meets the Solution Intent and the customer needs. The Solution Demo is typically held at the end of each Program Increment (PI), and may also be held more frequently depending on the Solution context and feedback mechanisms. References: Solution Demo - Scaled Agile Framework, SAFe for Teams - Know Your Role on an Agile Team | Scaled Agile, Exam Study Guide: SP (6.0) - SAFe Practitioner - scaledagile.com
NEW QUESTION # 117
What is one of the biggest benefits of decentralized decision-making?
- A. Removes accountability from leaders
- B. Ensures strategic decisions are made collaboratively
- C. Improves transparency
- D. Reduces delays
Answer: D
Explanation:
Explanation
Decentralized decision-making is one of the principles of the Lean-Agile mindset, which is the foundation of SAFe. It empowers teams and individuals to make decisions based on the local context and the best available information, rather than waiting for approval from higher authorities. This reduces delays, increases speed, and improves responsiveness to customer needs. It also fosters innovation, learning, and ownership of the outcomes. References: Lean-Agile Mindset, Unlock the Intrinsic Motivation of Knowledge Workers, Exam Study Guide: SP (6.0) - SAFe Practitioner
NEW QUESTION # 118
Who has content authority to make decisions at the User Story level during PI Planning?
- A. Release Train Engineer
- B. Product Owner
- C. Scrum Master/Team Coach
- D. Agile Team
Answer: B
Explanation:
Explanation
The Product Owner (PO) is the Agile team member primarily responsible for maximizing the value delivered by the team by ensuring that the team backlog is aligned with customer and stakeholder needs1. The PO has content authority to make decisions at the User Story level during PI Planning, as they are the team's primary customer advocate and primary link to business and technology strategy1. The PO also works with Product Management and other stakeholders to define the features and enablers that are part of the Program Backlog2. During PI Planning, the PO presents the team backlog, reviews and revises the draft plan, and defines and communicates the team PI objectives2. References: Product Owner, PI Planning
NEW QUESTION # 119
Which statement describes a cadence-based PI Planning event?
- A. As many team members as possible should attend remotely to reduce travel costs
- B. It is not a required event but tasks move forward at higher velocity when the meeting occurs
- C. It is an all-hands, two-day event with the goal to create alignment
- D. It is very important and should be postponed until all participants can attend
Answer: C
Explanation:
Explanation
A cadence-based PI Planning event is a face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and vision. It is essential to SAFe and should not be skipped or delayed. It is an opportunity for all team members and stakeholders to communicate, collaborate, and coordinate their work for the next Program Increment (PI), which is typically 8-12 weeks long. The PI Planning event has a standard agenda that includes a presentation of business context and vision, followed by team planning breakouts, where the teams create their Iteration plans and objectives for the upcoming PI. The event also includes a management review and problem-solving session, where the teams identify and resolve dependencies, risks, and impediments. The event concludes with a confidence vote and a final plan review, where the teams present their PI objectives and receive feedback from the business owners.
The PI Planning event is a key enabler of alignment, transparency, and collaboration across the ART. References: PI Planning, Planning Interval, PI Planning vs Sprint Planning: What Is the Ultimate Goal of the PI Planning Event?
NEW QUESTION # 120
What is the product vision?
- A. An explanation of the architectural runway needed to deliver products to the customer
- B. A method for aligning to the product direction
- C. A set of prioritized Features
- D. The user stories required to meet customer needs
Answer: B
Explanation:
Explanation
The product vision is a description of the future state of the product or service under development. It reflects customer and stakeholder needs, as well as the features and capabilities proposed to meet those needs. The product vision is both aspirational and achievable, providing the broader context and purpose of the product or service. It describes the markets, customer segments, user needs, and how the product or service will be different from the competition. The product vision is owned by the product owner, but its development requires input from stakeholders and the scrum team(s). The product vision helps align the team to the product direction and motivates them to deliver value to the customers and stakeholders. References: Vision, Solution Vision, An Insight Into 3 Types of Vision In SAFe, Product Vision | Agile Product Management, What is a Product Vision | Scrum.org Learn more
1blob:https://www.bing.com/887da8ea-10bc-44f4-a242-61b97911b7b4
v5.scaledagileframework.com2blob:https://www.bing.com/e2cea8b8-df2b-4b04-89c4-e68cf94d95e6 scaledagileframework.com
NEW QUESTION # 121
What type of visibility should Product Owners provide during the Agile Release Train Sync?
- A. Visibility into program Epics and Features
- B. Visibility into scope and priority adjustments
- C. Visibility into analysis, approval, and Feature readiness for implementation
- D. Visibility into backlog items
Answer: B
Explanation:
Explanation
The Agile Release Train Sync is a weekly meeting where the Release Train Engineer (RTE), Product Management, System Architect/Engineering, and Product Owners (POs) coordinate and communicate the current state of the Agile Release Train (ART). The POs provide visibility into the analysis, approval, and Feature readiness for implementation, which are the key aspects of managing the Program Backlog. The POs also share any dependencies, risks, or impediments that may affect the delivery of value by the ART. The Agile Release Train Sync helps align the teams and stakeholders on the vision, roadmap, and priorities of the solution. References: Agile Release Train, Product Owner, Program Backlog
NEW QUESTION # 122
What type of information can be easily seen in a cumulative flow diagram?
- A. Work in process across the team
- B. Time to complete a Feature
- C. Team capacity
- D. The number of defects that escape to production
Answer: A
Explanation:
Explanation
cumulative flow diagram (CFD) is a visual tool that shows the amount of work in each stage of a process over time. It helps teams identify bottlenecks, work in progress (WIP), and the overall progress of a project or program increment (PI). By looking at the width of the bands in a CFD, teams can easily see how much work is in each workflow state at any given time. This allows them to monitor and optimize their flow of value delivery. References: Cumulative Flow Diagram SAFe: Complete Guide, Measure and Grow - Scaled Agile Framework
NEW QUESTION # 123
The CALMR approach to DevOps includes Automation, Lean flow, Measurement, and Recovery. What does the "C" represent?
- A. Culture
- B. Continuous Integration
- C. Cadence
- D. Cycle-time
Answer: A
NEW QUESTION # 124
Which of the following is an output of the PI Planning process?
- A. PI Vision
- B. PI Objectives
- C. Actual PI Business Value
- D. PI Goals
Answer: B
Explanation:
Explanation
The PI Planning process is a two-day event that aligns all the teams on the Agile Release Train (ART) to a shared mission and vision for the upcoming Program Increment (PI)1. The PI Planning process has several inputs and outputs, as shown in Figure 12. One of the outputs of the PI Planning process is the PI Objectives, which are a set of SMART (Specific, Measurable, Achievable, Realistic, and Time-bound) goals that each team and the ART commit to achieving in the PI3. The PI Objectives are based on the features and enablers that the teams plan to deliver, and they reflect the business and technical value that the teams and the ART intend to provide to the stakeholders4. The PI Objectives are also used to track the progress and performance of the teams and the ART throughout the PI execution5. The other options are not outputs of the PI Planning process, but rather inputs or outcomes. The PI Vision is an input to the PI Planning process, which describes the current state, future state, and features of the solution that the ART will deliver in the PI. The PI Goals are an outcome of the PI Planning process, which are derived from the PI Objectives and summarize the business and technical benefits that the ART will deliver in the PI. The Actual PI Business Value is an outcome of the PI execution, which measures the actual value delivered by the ART at the end of the PI, based on the PI Objectives and stakeholder feedback. References: PI Planning - Scaled Agile Framework, Inputs and Outputs of PI Planning - Scaled Agile Framework, PI Objectives - Scaled Agile Framework, PI Planning - Scaled Agile Framework, Program Execution - Scaled Agile Framework, [PI Vision - Scaled Agile Framework], [PI Goals - Scaled Agile Framework], [Inspect and Adapt - Scaled Agile Framework] Figure 1. Inputs and outputs of PI Planning2
NEW QUESTION # 125
Team A has seven developers that can define and build any application the organization requires. Team A works with another team to test and deploy their work. Can Team A be considered a high-functioning Agile Team?
- A. No, because they are not cross-functional
- B. Yes, because they use another team to deploy
- C. No, because they have fewer than ten developers
- D. Yes, because they can build any application the organization requires
Answer: A
Explanation:
Explanation
A high-functioning Agile Team is a cross-functional group of typically ten or fewer individuals with all the skills necessary to define, build, test, and deliver value to their customer1. Team A is not cross-functional because they depend on another team to test and deploy their work, which creates handoffs and delays in the value delivery process. A cross-functional team should be able to perform all the activities required to deliver a potentially releasable increment of value in each iteration2. Team A should collaborate with the other team to integrate their testing and deployment capabilities and form a single Agile Team that can deliver value independently. References: Agile Teams - Scaled Agile Framework, 7 Qualities of High-Performing Agile Teams | AgileConnection
NEW QUESTION # 126
What is one action that occurs during iteration reviews for SAFe Scrum teams?
- A. Sizing unfinished stories
- B. Completing unfinished work
- C. Prioritizing unplanned work
- D. Evaluating current state metrics
Answer: D
Explanation:
Explanation
During iteration reviews, SAFe Scrum teams inspect the iteration increment, assess progress, and adjust the team backlog. One of the actions that occurs during this event is evaluating current state metrics, such as team velocity, quality, and customer satisfaction. These metrics help the team measure its performance and identify areas for improvement. Evaluating current state metrics also helps the team align its work with the iteration goals and the broader program increment objectives. References: Iteration Review, Team and Technical Agility
NEW QUESTION # 127
Which practices are demonstrated during the Inspect and Adapt event?
- A. Reflect, problem solve, and identify improvement actions
- B. Move forward, analyze future Stories, integrate, and iterate
- C. Forward focus, develop, cross-domain plan, and expedite execution
- D. New start, job sequence, funnel, and enable
Answer: A
Explanation:
Explanation
The Inspect and Adapt event is a significant event held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated by the train. Teams then reflect and identify improvement backlog items via a structured, problem-solving workshop. The Inspect and Adapt event consists of three parts: PI System Demo, Quantitative and qualitative measurement, and Retrospective and problem-solving workshop. The last part is where the practices of reflection, problem solving, and identifying improvement actions are demonstrated. The teams use a root cause analysis technique, such as the Five Whys, to identify the most critical impediments that impact their performance and quality. They then brainstorm and prioritize improvement actions that address the root causes and create SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) goals for implementing them in the next PI. The improvement actions are added to the Program Backlog and reviewed in the next PI Planning event. References: = Inspect and Adapt - Scaled Agile Framework, Scaled Agile Framework: Understand SAFe and Its 4 Core Values
NEW QUESTION # 128
What is one Story component to consider when estimating size?
- A. Scope
- B. Depth
- C. Knowledge
- D. Dependency
Answer: C
Explanation:
Explanation
Knowledge is one of the factors that affect the size of a story. It refers to what is known or unknown about the story, such as the requirements, the design, the technology, the domain, the dependencies, and the risks. The more unknowns there are, the larger the story size will be, as it will require more effort, complexity, and uncertainty to implement. Knowledge is one of the components of the story point estimation technique, which is a relative measure of the effort required to implement a story. Story points take into account the volume, complexity, knowledge, and uncertainty of the work. References: Story - Scaled Agile Framework, Story Point
- Scaled Agile Framework, How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog, Estimate Story - Quickscrum, Agile Estimation - Feature and Story Sizing Scales
NEW QUESTION # 129
What is a major benefit of reducing batch size?
- A. Increases visibility
- B. Increases work in process
- C. Increases throughput
- D. Decreases stress on the system
Answer: C
NEW QUESTION # 130
What are the four types of team topologies?
- A. Functional requirements, platform, enabling, and technical
- B. Stream-aligned, functional requirements, product domain, and technical
- C. Functional requirements, product domain, technical, and complicated subsystem
- D. Stream-aligned, platform, enabling, and complicated subsystem
Answer: D
Explanation:
Explanation
According to the book Team Topologies by Matthew Skelton and Manuel Pais, the four types of team topologies are stream-aligned, platform, enabling, and complicated subsystem. These team types are designed to optimize the flow of work and information in an organization, and to align with the principles of DevOps and agile. A stream-aligned team is focused on a single stream of work, such as a product, a feature, a user journey, or a user persona. A platform team provides the infrastructure and services that enable other teams to deliver value to customers. An enabling team helps other teams overcome obstacles and learn new skills and technologies. A complicated-subsystem team handles tasks that require specialized knowledge and expertise, such as mathematics, algorithms, or cryptography. References: Team Topologies: The 4 Team Types Explained | Shortform Books, Team Topologies | Atlassian, Key Concepts - Team Topologies, The Four Team Types from Team Topologies - IT Revolution, What are the core team types in Team Topologies?
NEW QUESTION # 131
What is used to capture the current state of the Portfolio and provide input for defining the future state?
- A. Portfolio Canvas
- B. Portfolio Kanban
- C. Portfolio Vision
- D. Portfolio Backlog
Answer: A
Explanation:
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. References: Business Model Canvas, Portfolio Vision
NEW QUESTION # 132
What is one of the five basic Agile quality practices applicable to all Agile Teams?
- A. Shift learning left
- B. Decentralized decision-making
- C. Creating the Architectural Runway
- D. Using non-functional requirements
Answer: A
Explanation:
Explanation
Shift learning left is one of the five basic Agile quality practices applicable to all Agile Teams. It means moving testing and validation activities as early as possible in the development process, to identify and fix defects before they become costly and risky. This practice improves quality, reduces waste, and accelerates delivery. References: Exam Study Guide: SP (6.0) - SAFe Practitioner, Built-in Quality, Lesson 4: Deliver Value
NEW QUESTION # 133
On the seventh day of the Iteration, the team realizes that they will not complete 5 of the 13 Stories. The Product Owner (PO) says she cannot negotiate the scope of the remaining Stories any further. What is the PO's best course of action?
- A. Have an emergency Iteration Planning meeting
- B. Defer acceptance testing to the next Iteration
- C. Stop the current Iteration and plan a new Iteration with the new knowledge
- D. Communicate the status of the Iteration to all stakeholders
Answer: D
Explanation:
Explanation
The PO's best course of action is to communicate the status of the Iteration to all stakeholders, including the other teams on the Agile Release Train (ART), the Release Train Engineer (RTE), the System Architect/Engineer, the Product Management, and the Business Owners. This will help to align expectations, manage dependencies, and mitigate risks. The PO should also collaborate with the team and the stakeholders to prioritize the remaining work and identify the most valuable Stories to deliver by the end of the Iteration.
The PO should not defer acceptance testing to the next Iteration, as this would violate the Definition of Done and compromise the quality of the system increment. The PO should not have an emergency Iteration Planning meeting, as this would disrupt the cadence and synchronization of the ART and waste time and resources. The PO should not stop the current Iteration and plan a new Iteration with the new knowledge, as this would also disrupt the cadence and synchronization of the ART and create confusion and uncertainty.
References: Team Backlog - Scaled Agile Framework, Iteration Planning - Scaled Agile Framework, Iteration Execution - Scaled Agile Framework
NEW QUESTION # 134
What is one of the six steps in the Problem Solving Workshop?
- A. Identify the biggest root cause using the Pareto Analysis
- B. Choose a problem to solve-agreement not required
- C. Brainstorm possible failures
- D. Apply root solution analysis
Answer: B
Explanation:
Explanation
he Problem Solving Workshop is a structured approach to identifying the root cause and actions to address systemic problems. It is part of the Inspect and Adapt event that occurs at the end of each Program Increment.
The six steps in the Problem Solving Workshop are:
Choose a problem to solve-agreement not required: The Release Train Engineer (RTE) facilitates a brainstorming session to generate a list of potential problems that affect the ART's performance. The participants use dot voting to prioritize the problems and select the most important one to solve.
Agreement is not required, as the majority vote determines the problem to focus on.
Perform root cause analysis: The RTE leads the team in applying the 'Five Whys' technique to drill down to the root cause of the problem. The team asks 'why' repeatedly until they reach a cause that is actionable and within their control.
Brainstorm solutions: The team generates a list of possible solutions to address the root cause. They use divergent thinking to come up with as many ideas as possible, without judging or evaluating them.
Decide on the best solution: The team uses convergent thinking to narrow down the list of solutions and select the best one. They can use criteria such as feasibility, impact, cost, and alignment with the SAFe Principles and Values to evaluate the solutions.
Define and visualize the improvement backlog items: The team defines the improvement backlog items that will implement the chosen solution. They write them in the format of 'As a [role], I can [action], so that [outcome]'. They also visualize the items on a Kanban board or a similar tool to track their progress and status.
Assign owners and agree on the SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goals: The team assigns owners to each improvement backlog item and agrees on the SMART goals that will measure the success of the solution. They also define the acceptance criteria and the expected benefits of the improvement.
References: Inspect and Adapt - Scaled Agile Framework, Problem-solving workshop: Step-by-Step - Agilephoria, SAFe for Teams Student Workbook: materials and exercises from Lesson 7, Exam Study Guide:
SP (6.0) - SAFe Practitioner
NEW QUESTION # 135
......
SAFe for Teams SP (6.0) - SAFe Practitioner Free Update Certification Sample Questions: https://exam-hub.prepawayexam.com/Scaled-Agile/braindumps.SP-SAFe-Practitioner.ete.file.html