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 customer 1 . 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 iteration 2 . 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

The Portfolio Kanban system is a method to visualize and manage the flow of portfolio Epics, from ideation through analysis, implementation, and completion 1 .  The analyzing step of the Portfolio Kanban system involves developing a Lean business case for the Epic and presenting it to Lean Portfolio Management (LPM) for approval 1 .  If the Epic receives a ‘go’ decision from LPM, it will be moved to the ready state in the Portfolio Kanban, where it will wait until one or more Agile Release Trains (ARTs) have the capacity to implement it 1 . The other options are incorrect because:

A. The Epic Owner does not have the authority to approve the Lean business case.  Only LPM can make the final decision on whether to proceed with the Epic or not 1 .

C. The Epic will not remain in the analyzing step after receiving a ‘go’ decision from LPM.  It will be moved to the ready state, where it will be prioritized using weighted shortest job first (WSJF) and other factors 1 .

D. The Epic will not be implemented based on its WSJF ranking alone.  It will also depend on the availability and alignment of the ARTs that can deliver the Epic 1 .  References :  1 :  Portfolio Kanban - Scaled Agile Framework

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 1 .  One of the aspects of culture is to establish a work environment of shared responsibility, where everyone in the value stream is accountable for the quality and security of the solution, and for the outcomes delivered to the customer 2 .  This means breaking down the silos and barriers between development, operations, security, and other teams, and creating a culture of mutual trust and respect 3 .  Shared responsibility also means that everyone in the value stream has the authority and autonomy to make decisions and take actions that support the delivery of value, while following the guardrails and policies established by the enterprise 4 .  References :  CALMR - Scaled Agile Framework ,  Culture - Scaled Agile Framework ,  What Is DevOps? - Scaled Agile Framework ,  Decentralize Decision Making - Scaled Agile Framework

 The daily stand-up is a 15-minute meeting that occurs every day during the Iteration, where the Agile team members synchronize their work, share their progress, and identify any impediments or dependencies. The daily stand-up follows a simple format, where each team member answers three questions:

What did I do yesterday to advance the Iteration goals?

What will I do today to advance the Iteration goals?

Are there any impediments that will prevent the team from meeting the Iteration goals? These questions help the team members to align their actions with the Iteration goals, communicate their status and plans, and raise any issues or risks that need to be addressed. The daily stand-up also fosters collaboration, accountability, and transparency among the team members, and enables them to adjust their work as needed to deliver value.  References :  Exam Study Guide: SP (6.0) - SAFe® Practitioner ,  Daily Stand-up

An ART event is a meeting or ceremony that involves all the teams in an Agile Release Train (ART) and helps them align, collaborate, and deliver value. An example of an ART event is the Innovation and Planning (IP) Iteration, which is a two-week period at the end of each Program Increment (PI) that provides time for innovation, planning, and improvement activities. During the IP Iteration, teams can explore new ideas, work on technical debt, conduct hackathons, prepare for the next PI Planning, and conduct the Inspect and Adapt workshop.  References :  Agile Release Train ,  Scaled Agile: ART Events Overview , Innovation and Planning Iteration

The principle that includes “working software is the primary measure of progress” is one of the twelve principles behind the Agile Manifesto. The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development movement. The value that corresponds to this principle is “working software over comprehensive documentation”. The principle states that the ultimate goal of any software development project is to deliver working software that satisfies the customer’s needs and expectations, and that any other intermediate or auxiliary artifacts, such as plans, documents, models, or reports, are secondary and should not distract from the main objective. The principle also implies that working software should be delivered frequently and continuously, and that the progress of the project should be measured by the amount and quality of the software delivered, not by the adherence to a predefined plan or schedule.  References :  Principles behind the Agile Manifesto ,  Agile Manifesto - Scaled Agile Framework

 Agile Teams are the basic building block when organizing around value in SAFe. They are cross-functional, self-organizing, and empowered to deliver value in short iterations. They are aligned to a common mission and vision through the Agile Release Train (ART), which is a long-lived team of Agile Teams that delivers value streams. Agile Teams apply Scrum, Kanban, and XP practices to collaborate and deliver solutions that meet customer needs and provide business value.  References :  Agile Teams ,  Agile Release Trains ,  Exam Study Guide: SP (6.0) - SAFe Practitioner

A program board is a visual summary of the features or goals, when they need to be reached, and any cross-team dependencies impacting their delivery. The program board helps teams within the Agile Release Train (ART) to coordinate their work and communicate their plan to the entire organization. One of the main purposes of the program board is to help teams identify and manage dependencies between teams, which can affect the delivery of value and increase the risk of delays or failures. By visualizing and tracking dependencies on the program board, teams can avoid or resolve them during the Program Increment (PI) planning event or throughout the PI execution.  References :  SAFe Program Board 101: Everything You Need To Know ,  SAFe Program Board: Good Practices for SAFe PI Planning ,  Tips for using a SAFe program board

Resizing the work means breaking down large batches of work into smaller, more manageable pieces that can be completed faster and with less variability. This reduces the queue length, which is the number of work items waiting to be processed, and improves the flow of value delivery. Resizing the work is one of the principles of Lean-Agile development, and it is also a practice of Scrum and Kanban teams.  References :  Exam Study Guide: SP (6.0) - SAFe® Practitioner ,  Visualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengths ,  ScrumXP ,  Story

n : A backlog refinement session is a periodic activity teams use to define, discuss, estimate, and establish acceptance criteria for upcoming backlog items 1 . One key benefit of a backlog refinement session is that it provides time to identify dependencies and issues that could impact the next iteration. By doing so, teams can reduce uncertainty, avoid surprises, and plan more effectively.  Backlog refinement also helps surface problems with the current plan, which may require discussion at the team, PO, or coach syncs 2 .  Additionally, backlog refinement helps teams align their backlog with the ART backlog, the PI objectives, and the customer needs 2 .  References :  Backlog Refinement - Scaled Agile Framework ,  Team Backlog - Scaled Agile Framework