= 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

 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

 SAFe Team Kanban is a type of SAFe Agile Team that relies on a continually-refined Team Backlog as the primary input to drive value delivery. SAFe Team Kanban is a method that helps teams manage and improve the flow of value across the Continuous Delivery Pipeline. It is based on the principles of Lean and Kanban, which aim to optimize the system, limit work in progress (WIP), implement feedback loops, and empower the team. SAFe Team Kanban uses a visual board to track the flow of work from the Team Backlog to the Done state. The Team Backlog is a subset of the Program Backlog that contains the user stories, enablers, and defects that the team needs to work on. The Team Backlog is constantly refined and prioritized by the Product Owner, who collaborates with the team and other stakeholders to ensure that the most valuable and feasible work items are selected for implementation.  References :  Team Kanban - Scaled Agile Framework ,  Team Kanban - Scaled Agile Framework

 = The “3 Cs” of user stories are three criteria that help to ensure that the requirements in your story are clear, complete, and correct.  These three criteria are Card, Conversation, and Confirmation 1 .

Card: A user story card is a placeholder for a conversation. It is a brief and informal description of a software feature written from the perspective of the end user. It captures the essence of the user’s need, without going into too much detail or technical jargon.  It is usually written on a physical or digital card that can be easily moved and prioritized 2 .

Conversation: A user story card is not enough to convey all the information needed to develop and deliver the feature. It is meant to trigger a conversation between the product owner, the development team, and other stakeholders. The conversation is where the details, assumptions, risks, and acceptance criteria are discussed and clarified.  The conversation is also an opportunity to collaborate, negotiate, and validate the user story 3 .

Confirmation: A user story is not complete until it has a confirmation. This is a set of criteria that define what done looks like for the feature. It is also known as acceptance criteria, and it specifies the conditions that must be met for the user story to be accepted by the product owner and the customer.  The confirmation is usually written as a series of testable statements that can be verified by the development team and the product owner 4 .

An effective Scrum Master is a servant leader who helps the team self-organize, collaborate, and deliver value. They also exhibit Lean-Agile Leadership by embracing the SAFe Core Values, Principles, and Practices, and by coaching the team and stakeholders on how to apply them. Additionally, an effective Scrum Master facilitates the team’s progress toward the Iteration goals by removing impediments, ensuring alignment with the Product Owner and other teams, and fostering continuous improvement.  References :  Scrum Master - Scaled Agile Framework ,  SAFe for Teams Student Workbook: materials and exercises from Lesson 2 ,  Exam Study Guide: SP (6.0) - SAFe® Practitioner

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 learning 1 2 .  References :  Story - Scaled Agile Framework , [What is User Story? -

 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

 Empathy maps are a design thinking tool that promotes customer identification by helping teams develop a deep, shared understanding of others. They enable teams to imagine what a specific persona is thinking, feeling, hearing, and seeing as they use the solution. Empathy maps help teams to design with empathy, which is a key behavior of customer centricity. Empathy maps can be used to explore different aspects of the problem and solution space, and to validate assumptions and hypotheses about the customer’s needs and preferences.  References :  Design Thinking ,  Customer Centricity

Relentless improvement is one of the four SAFe Core Values, which are the guiding principles that help individuals and organizations achieve Business Agility 1 .  Relentless improvement means that everyone in the organization is committed to continuously learning, growing, and innovating, and that they embrace a culture of experimentation, feedback, and problem-solving 2 . By inviting every team member to work on any project they choose during the Innovation and Planning Iteration, the organization is demonstrating relentless improvement, as they are providing time and space for people to explore their creative ideas, learn new skills, and collaborate with others outside their usual teams.  This can lead to better solutions, higher engagement, and faster adaptation to changing customer and market needs 3 4 .  References : =  1 : SAFe Core Values - Scaled Agile Framework 5 ;  2 : Relentless Improvement - Scaled Agile Framework;  3 : Innovation and Planning Iteration - Scaled Agile Framework;  4 : How to Implement Quality in a Lean-Agile Environment Successfully

According to SAFe Lean-Agile Principle #10, the enterprise should organize around value to deliver the best value and quality for people and society in the shortest sustainable lead time. This means that the enterprise should create a network of development value streams that can optimize the flow of value by reducing handoffs and delays, bringing together all the necessary personnel, providing intense customer focus, and measuring success by outcome-based key performance indicators. Moreover, the network should be able to rapidly reorganize as necessary to support emerging opportunities and competitive threats, while leveraging the hierarchical system for benefits and stability. Therefore, the correct answer is D. Reorganize the network to address emerging opportunities.  References :  Principle #10 – Organize around value - Scaled Agile Framework ,  SAFe Lean-Agile Principles - Scaled Agile Framework ,  The 10th Principle – Lean Agile Guru