Lean flow is one of the elements of the CALMR approach to DevOps in SAFe. It means applying lean principles and practices to optimize the flow of value from idea to production. Lean flow accelerates delivery by eliminating waste, reducing batch sizes, implementing pull systems, limiting work in process, managing queues, reducing handoffs, and applying cadence and synchronization. Lean flow enables faster feedback, shorter lead times, higher quality, and lower costs. (Must be taken from SAFe 6 Scrum Master resources)

CALMR - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline

One benefit of having an IP Iteration every PI is that it creates an estimating buffer for meeting PI objectives. PI objectives are a set of SMART goals that align the teams and stakeholders to a common vision and mission for the upcoming Program Increment (PI).They are derived from the business context, priorities, and dependencies, and are agreed upon and committed by the teams during PI Planning1However, since PI objectives are based on estimates and assumptions, there is always a degree of uncertainty and variability in the delivery process. To account for this, SAFe recommends that teams reserve 10% of their capacity for each PI as an estimating buffer.This buffer is used during the IP Iteration, which is a unique, dedicated iteration that occurs every PI and provides dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events2By having an IP Iteration as an estimating buffer, the teams can improve the predictability and flow of value delivery, as well as reduce the stress and pressure of meeting the PI objectives23(Must be taken from SAFe 6 Scrum Master resources)

PI Objectives - Scaled Agile Framework

Innovation and Planning Iteration - Scaled Agile Framework

SAFe Scrum Master Course Outline

One purpose of iteration goals is to align team members to a common purpose and vision. Iteration goals are a high-level summary of the business and technical goals that an Agile Team agrees to accomplish in an iteration. They help the team and the product owner to reach agreement on the business value they intend to deliver, align their work to their team PI objectives, and ground everyone on their shared purpose. Iteration goals also provide transparency and management information, as well as support the coordination and dependency management of the Agile Release Train (ART).

Iteration Goals - Scaled Agile Framework

Exam Study Guide: SSM (6.0) - SAFe Scrum Master

One benefit of PI Planning is that it allows for faster decision-making by bringing together all the members of the Agile Release Train (ART) and the relevant stakeholders in a face-to-face (or virtual) event. PI Planning provides an opportunity for the ART to align on a common vision and mission, review the business context and priorities, identify and resolve dependencies and risks, and commit to a realistic and achievable plan for the next Program Increment (PI). By having everyone involved in the planning process, the ART can leverage the collective knowledge and expertise of the participants, reduce ambiguity and uncertainty, and make informed and timely decisions that support the delivery of value to the customers. (Must be taken from SAFe 6 Scrum Master resources)

PI Planning - Scaled Agile Framework

Planning Interval (PI) - Scaled Agile Framework

Preparing for PI Planning | Checklist for Scrum Masters and Product ...

Scrum Master - Scaled Agile Framework

Scrum Master role in PI Planning - ValueGlide

Backlog Refinement is the Agile Team event where team members estimate relative story sizes.Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single iteration2To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35(Must be taken from SAFe 6 Scrum Master resources)

Team Backlog - Scaled Agile Framework

Backlog Refinement - Scaled Agile Framework

Story - Scaled Agile Framework

How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog

Why Your Agile Team Should Use Relative Story Point Estimation