Pass the Scaled Agile SAFe for Teams SP-SAFe-Practitioner Questions and answers with ExamsMirror

Lean Thinking is a philosophy that aims to create value for customers by eliminating waste and unnecessary steps in company processes. One of the main sources of waste is delay, which can be caused by long lead times, large batch sizes, excessive inventory, poor quality, and lack of coordination. Reducing delays can improve customer satisfaction, increase efficiency, and lower costs. Lean Thinking is based on two pillars: respect for people and continuous improvement. Respect for people means empowering and engaging employees, customers, and stakeholders to participate in problem-solving and innovation. Continuous improvement means constantly seeking ways to improve the process and the product by applying the Plan-Do-Check-Act cycle and the scientific method. References: Lean-Agile Mindset - Scaled Agile Framework, Lean Thinking: Overview, Principles, Benefits, & Applications Explained, The Focus of Lean - Collin College, What is Lean? - Project Management Institute

n: Agile development is more beneficial than waterfall development because it increases productivity and employee engagement by empowering teams to self-organize, collaborate, and deliver value in small increments. It also allows businesses to deliver value to the market more quickly by reducing the feedback cycle, adapting to changing requirements, and releasing high-quality products frequently. References: SAFe® for Teams - Know Your Role on an Agile Team, Exam Study Guide: SP (6.0) - SAFe® Practitioner, Lean-Agile Mindset, Continuous Delivery Pipeline

= A cumulative flow diagram (CFD) is a tool used to visualize the flow of work in a process over time. It shows the quantity of work in different stages or states, such as backlog, in progress, done, etc. A CFD helps to monitor the work in process (WIP) across the whole team, as well as the arrival and departure rates of work items. A CFD can also reveal bottlenecks, queues, variability, and cycle time in the process. References: = Cumulative Flow Diagram - Scaled Agile Framework, Cumulative flow diagram - Wikipedia, Cumulative Flow Diagram - What Information Does It Provide - Kanban Zone

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

 One of the activities that occurs during the PI Planning event is the identification and analysis of the potential risks that may affect the delivery of value by the Agile Release Train (ART). The risks are categorized using the ROAM board, which stands for Resolved, Owned, Accepted, and Mitigated. The Managed category is a subset of the Mitigated category, where the risks are assigned to owners who are responsible for monitoring and controlling them throughout the PI. The Managed category addresses the potential risks that cannot be resolved, owned, or accepted, but can be reduced or avoided by applying appropriate strategies and actions. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, ROAMing Risks

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, the purpose of Iteration Planning is to plan the work that the team will commit to deliver in the Iteration. The team collaborates with the Product Owner to select the Stories from the Team Backlog, define the acceptance criteria, break them into tasks, estimate the effort, and identify the dependencies and risks. The team also defines the Iteration goals and the Iteration backlog, which reflect the scope of the Iteration. The Iteration Planning ensures that the team has a clear and realistic plan to deliver value in the Iteration. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe® for Teams - Know Your Role on an Agile Team, [Iteration Planning]

https://v5.scaledagileframework.com/iteration-planning/

The team’s initial capacity before calculating for time off is 48. This is based on the following formula: Give the team 8 points for every full-time developer and tester on the team. Since the team has two testers and three developers, that is 5 x 8 = 40 points. Then, add one point for every 10% of the Product Owner’s time dedicated to the team. Since the Product Owner is split between two teams, that is 0.5 x 10 = 5 points. Finally, add one point for every 10% of the Scrum Master/Team Coach’s time dedicated to facilitating the team. Since the Scrum Master/Team Coach is full-time, that is 1 x 10 = 10 points. The total is 40 + 5 + 10 = 55 points. However, since the team should not plan to 100% capacity, a buffer of 15% is recommended. Therefore, the final initial capacity is 55 x 0.85 = 46.75, which can be rounded up to 48 points. References: Iteration Planning, How to calculate the capacity, How to Estimate Capacity for Work in Agile Teams, SAFe Agile Planning - Plan Less than 100% Capacity, How to Improve Your Agile Team’s Capacity Planning

 Culture is the first element of the CALMR approach to DevOps in SAFe. It refers to the shared mindset and values that support successful DevOps adoption. Culture in SAFe is influenced by the Lean-Agile principles and practices that guide the entire framework. Culture in DevOps requires customer-centricity, collaboration, trust, empowerment, learning, and feedback among all the stakeholders involved in the value stream. Culture also fosters a shift-left mentality, where operational and quality concerns are addressed early and often in the development process. Culture is the foundation for the other elements of CALMR: automation, lean flow, measurement, and recovery. References: CALMR - Scaled Agile Framework, The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

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

The Inspect and Adapt workshop 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 train1. The first part of the workshop is the PI System Demo, which shows all the Features that the Agile Release Train (ART) has developed over the course of the PI2. The other options are not activities that occur during the Inspect and Adapt workshop. Refining the ART backlog is a continuous process that happens throughout the PI3. A retrospective of the Iteration is a team-level event that happens after every Iteration4. Planning the next PI is a separate event that happens before the start of the next PI.