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

Answer : D

A System Demo is one way to show true progress of business outcomes. A System Demo is a significant event that provides an integrated view of new features for the most recent iteration delivered by all the teams in the Agile Release Train (ART). The System Demo is attended by customers, stakeholders, and ART members, who evaluate the system and provide feedback. The System Demo is a key measure of solution quality, customer value, and ART velocity. It also helps to validate the alignment of the PI Objectives with the business outcomes.Reference:System 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

Answer : C

SAFe Implementation Roadmap is a template for putting SAFe into practice within an organization. It consists of an overview graphic and a 14-article series that describes a strategy and an ordered set of activities for successfully implementing SAFe. The roadmap is based on proven organizational change management strategies and successful adoption patterns from hundreds of the world's largest enterprises. The roadmap helps leaders and change agents to script the critical moves, create a sense of urgency, build a guiding coalition, form a strategic vision, enlist a volunteer army, enable action by removing barriers, generate short-term wins, sustain acceleration, and institute change.Reference:Implementation Roadmap - Scaled Agile Framework,SAFe for Teams - Know Your Role on an Agile Team | Scaled Agile

Answer : D

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

Answer : B

According to theScaled Agile Framework, the ART Planning Board is a visualization of the PI's feature delivery dates, feature dependencies among teams, and relevant milestones1.Features are the primary elements that are planned and tracked on the ART Planning Board2.

Epics, user stories, and tasks are not found on the ART Planning Board, but they are related to features in different ways.Epics are large initiatives that span multiple ARTs and PIs, and they are decomposed into features and enablers2.User stories and tasks are smaller units of work that are used by teams to implement features within iterations2.

Answer : C

Transparency is one of the four core values of SAFe that represents the foundational beliefs that are key to SAFe's effectiveness. Transparency means making all the work visible, along with its priorities, status, dependencies, and outcomes. Transparency also means being honest and open about the challenges, risks, failures, and learnings that occur during the development process. By stating the reason for the release failure and sharing their improvement plan, Team B is demonstrating transparency to the other teams and stakeholders in the System Demo. Transparency helps to build trust, collaboration, alignment, and continuous learning in the ART and the Solution Train.Reference: =Core Values - Scaled Agile Framework,System Demo - Scaled Agile Framework,Exam Study Guide: SP (6.0) - SAFe Practitioner

Answer : B

= WIP limits are necessary in the ART Kanban to ensure large queues are not forming, which would slow down the flow of value and increase the lead time. WIP limits are a way of applying the Lean principle of reducing waste and optimizing the system for the whole. By limiting the amount of work that can be in progress at any stage of the Kanban system, the ART can balance the demand and capacity, avoid overloading the system, and focus on completing the work rather than starting new work. WIP limits also help to expose bottlenecks, dependencies, and impediments that need to be resolved to improve the flow efficiency and quality of the work.Reference: =ART Flow - Scaled Agile Framework,ART and Solution Train Backlogs - Scaled Agile Framework,Kanban And The Importance Of Work In Progress (WIP) Limits

Answer : C

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