Scaled Agile SAFe for Teams SP (6.0) - SAFe Practitioner SP SAFe Practitioner Exam Questions

Page: 1 / 14
Total 269 questions
Question 1

What is the first step in Kotter's 8-step process for leading change?



Answer : C

According to Kotter's 8-step process for leading change, the first step is to create a sense of urgency among both managers and employees. This means making them aware of the existing problems or opportunities that require change, and motivating them to act with passion and purpose. Creating a sense of urgency helps to overcome complacency, resistance, and fear of change, and builds momentum for the change initiative.Reference:Kotter's 8-step process for leading change,The Easy Guide to Kotter's 8 Step Change Model,John Kotter's Eight Step Change Model,Kotter's 8 step Model of Change,How to Successfully Implement Kotter's 8 Step Change Model


Question 2

Volume, complexity, knowledge, and uncertainty are all qualities of what?



Answer : C

Story points are a relative measure of the effort required to implement a user story. They take into account the volume, complexity, knowledge, and uncertainty of the work. Volume refers to how much work there is, complexity refers to how hard it is, knowledge refers to what is known or unknown, and uncertainty refers to the risk or variability involved. Story points help agile teams estimate their work and plan their iterations.Reference:Story - Scaled Agile Framework,Story Point - Scaled Agile Framework,Understanding complexity | Range


Question 3

Which pillar in the House of Lean focuses on the Customer being the consumer of the work?



Answer : A

Value is the first and most important pillar in the House of Lean, which is a model that guides the Lean-Agile transformation and culture.Value means delivering the maximum benefit to the customer in the shortest sustainable lead time, while providing the best quality and lowest cost possible1.Value is the ultimate goal of the House of Lean, and it is achieved by applying the other pillars: innovation, relentless improvement, leadership, and respect for people and culture2.Value is also the foundation of the Lean-Agile mindset, which is the way of thinking and acting that enables Business Agility3.Value focuses on the customer as the consumer of the work, and requires understanding and meeting their needs, expectations, and desires4.Reference: =1: SAFe Core Values - Scaled Agile Framework1;2: The SAFe House of Lean model: short and sweet - Echometer2;3: Lean-Agile Mindset - Scaled Agile Framework3;4: Exploring Which Pillar in the House of Lean Focuses on the Customer4


Question 4

A team finishes developing all of their Stories in the first six days of the Iteration, tests them in the following two days, and fixes bugs in the days remaining. How is the team behaving?



Answer : C

: The team is waterfalling the Iteration, which means they are following a sequential and rigid process of development, testing, and fixing, instead of an iterative and incremental approach. This is not aligned with the Agile principles and practices, which advocate for delivering working software frequently, with continuous feedback and improvement. Waterfalling the Iteration reduces the team's ability to respond to change, deliver value, and collaborate effectively. It also increases the risk of accumulating technical debt, defects, and rework.Reference:Iteration Execution - Scaled Agile Framework,SCALING: SP - SAFe for Teams 4.6 Flashcards - Brainscape


Question 5

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



Answer : B

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 deliveryReference:Exam Study Guide: SP (6.0) - SAFe Practitioner,Team Events,PI Events,Sync Events, [Program Events]


Question 6

Which of the following Story components captures details on testing for completion?



Answer : C

Acceptance criteria are the conditions that a story must satisfy to be accepted by the Product Owner and the stakeholders. They define the boundaries of the story and provide guidance on how to test it for completion. Acceptance criteria are usually written as a list of statements or scenarios that describe the expected behavior and outcomes of the story.They help to ensure that the story delivers value to the user and meets the Definition of Done1234.Reference:Story - Scaled Agile Framework,How to Write Agile Test Case Requirements | SmartBear,Agile Story Completion Checklist - SDLCforms,Module 2: Complete a story - IBM


Question 7

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?



Answer : B

: = 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.Reference: =Agile Teams - Scaled Agile Framework,Core Values - Scaled Agile Framework,SAFe Principles - Scaled Agile Framework,Exam Study Guide: SP (6.0) - SAFe Practitioner


Page:    1 / 14   
Total 269 questions