Scrum Updated SAFe-Practitioner Exam Questions and Answers by benny

 SAFe recommends using a second operating system to deliver value by creating a dual operating system that consists of a Network and a Hierarchy. The Network is optimized for speed and adaptability, while the Hierarchy is optimized for efficiency and stability. The Network is composed of development value streams (DVSs) that are realized by product-focused Agile Release Trains (ARTs). The ARTs are cross-functional teams that work together to deliver software products on a regular schedule. The Hierarchy provides the necessary support and governance for the Network, such as operations, HR, finance, and compliance. By using a second operating system, SAFe enables business agility by allowing the organization to organize and reorganize around the flow of value, while maintaining the benefits and stability of the existing hierarchical structure. References: Business Agility, Principle #10 – Organize around value, How Does SAFe Enable Business Agility Through A Second Operating System, How does safe provide a second operating system that enables business agility

= The Agile Team responsibility that is associated with the Iteration Retrospective is “Improve relentlessly”. This responsibility reflects the SAFe Core Value of Relentless Improvement, which means that the team continuously reflects on their practices, identifies improvement opportunities, and implements them in the next iteration. The Iteration Retrospective is a regular event where the team members discuss the results of the iteration, review their practices, and identify ways to improve. The team uses various techniques to collect feedback, perform root cause analysis, and prioritize improvement actions. The improvement actions are added to the Team Backlog and reviewed in the next Iteration Planning event. References: = Relentless Improvement - Scaled Agile Framework, Iteration Retrospective - Scaled Agile Framework1

The ART planning board, also known as the program board, is a visualization of the PI’s feature delivery dates, feature dependencies among teams, and relevant milestones. It helps the ART align on a common mission and vision, identify and resolve dependencies, and track progress and risks throughout the PI. The ART planning board does not show risks, capacity and load, or epics, although these may be discussed or tracked elsewhere during PI planning or execution. References: ART Planning Board, PI Planning, SAFe Program Board 101

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