Scrum Updated SAFe-Practitioner Exam Questions and Answers by ria

The Team and Technical Agility Core Competency describes the critical skills and Lean-Agile principles and practices that high-performing Agile teams and Teams of Agile teams use to create high-quality solutions for their customers. It consists of three dimensions: Agile Teams, Team of Agile Teams, and Built in Quality1. Built in Quality is the dimension that ensures that every aspect of the solution, from code to compliance, is designed and implemented with high standards and practices that guarantee quality. Built in Quality enables fast and reliable delivery of value, reduces waste and rework, and fosters a culture of continuous improvement. Some of the practices that support Built in Quality in SAFe are Test-First, Behavior-Driven Development, Acceptance Test-Driven Development, Continuous Integration, Continuous Deployment, and Communities of Practice2. References: Team and Technical Agility - Scaled Agile Framework, Built-In Quality - Scaled Agile Framework.

= Decoupling deployment from release means having the ability to deploy changes to a system without having to make a new release of the system. This can be a valuable capability when making changes to a system that is in production and needs to be rolled back quickly if there are problems. It also allows releasing functionality on demand to meet business needs, which is one of the aspects of the Continuous Delivery Pipeline in SAFe. By decoupling deployment from release, enterprises can achieve faster feedback, higher frequency, and greater safety in delivering value to customers. References: = Release on Demand, DevOps: Why Is It Important to Decouple Deployment From Release?, Why Is It Important to Decouple Deployment from Release?, What a Lovely Decouple: Why Decoupling Deploy from Release Is a Game Changer

According to SAFe, an Agile team is a cross-functional group of 5-11 individuals who define, build, test, and deliver an increment of value in a short time box1. This size allows for enough diversity of skills and perspectives while still allowing for close collaboration and communication among team members. Larger teams tend to have more communication overhead, coordination challenges, and reduced productivity. Smaller teams may lack some of the necessary skills or perspectives to deliver value effectively. References: Agile Teams - Scaled Agile Framework, What is the Recommended Size of an Agile Team? - StuffSure, The Number 7: Why is it so important? - agile42

Assigning the same business value to all PI Objectives is an anti-pattern because it does not reflect the relative importance and priority of each objective. It also does not provide a clear guidance for trade-off decisions and impediment resolution. Business value should be assigned based on the expected benefits and outcomes of each objective, and it should be negotiated and agreed upon by the Business Owners and the teams. References: SAFe for Teams Student Workbook: materials and exercises from Lesson 4; [v6.scaledagileframework.com/team-pi-objectives/]