One of the tools associated with Design Thinking is empathy maps, which are a visual way to capture and organize the user’s needs, goals, pains, and gains. Empathy maps help the team to understand the user’s perspective, empathize with their emotions, and design solutions that address their problems and aspirations. Empathy maps are typically created during the Discover phase of Design Thinking, where the team conducts user research and synthesizes the findings.  References :  SAFe for Teams Student Workbook : materials and exercises from Lesson 1;  v5.scaledagileframework.com/design-thinking/ ;  v5.scaledagileframework.com/get-feedback/

  According to the SAFe Implementation Roadmap, culture change is the last step in the transformation process. It states that “culture change comes last, not first.  You can’t change a culture until you have changed the underlying behavior and the results that the behavior produces”  1 . Therefore, the best way to change the culture is to adopt new approaches that deliver better outcomes and then anchor them in the culture by reinforcing the benefits and values they bring.  This is consistent with Kotter’s model of leading change, which also suggests that anchoring new approaches in the culture is the final stage of a successful change effort  2 3 .  References :  Enhance the Portfolio ,  Leading Change (Step 8) – Anchor Change in the Culture ,  Anchor Change in Your Organization’s Culture

SAFe recommends running a Retrospective on a cadence during the PI for SAFe Team Kanban Teams. A Retrospective is a team-level event that occurs at the end of each iteration, where the team reflects on how they are working and identifies improvement actions for the next iteration.  A Retrospective helps the team pursue perfection by applying the Plan-Do-Check-Adjust (PDCA) cycle 1 .  SAFe Team Kanban Teams also participate in other ART events, such as PI Planning, System Demo, and Inspect and Adapt 2 .  References :  1 :  Retrospective - Scaled Agile Framework 2 :  SAFe Team Kanban - Scaled Agile Framework

A modified Fibonacci sequence is a relative estimating number sequence that reflects the inherent uncertainty of the job being estimated. It is based on the original Fibonacci sequence, which is a mathematical series of numbers where each number is the sum of the two preceding ones, starting from 0 and 1. The modified Fibonacci sequence, however, rounds up the larger numbers to avoid questions about why something is 21 instead of 20 or 34 instead of 40. The modified Fibonacci sequence is commonly used in Agile estimation techniques, such as Planning Poker, to assign story points to user stories or other backlog items. The sequence is: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100.  References :  Modified Fibonacci Sequence - Scaled Agile Framework ,  Fibonacci Agile Estimation: What Is It and Why Does it Work? - Parabol

= 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

Building incrementally with fast, integrated learning cycles is one of the ten SAFe Lean-Agile Principles. It means that the enterprise delivers value in small batches of work, frequently and reliably, to provide fast feedback and foster innovation. By building incrementally, the enterprise can reduce risk, complexity, and uncertainty, and validate assumptions before committing to large investments. By integrating frequently, the enterprise can ensure quality, collaboration, and alignment across the value stream.  By creating learning cycles, the enterprise can test hypotheses, measure outcomes, and pivot as needed to achieve the desired results 1 .  References :  1 :  Build Incrementally with Fast, Integrated Learning Cycles - Scaled Agile Framework

 WIP stands for work in process, which is the amount of work that is currently being done in a system. One way to understand WIP is to make it visible to all stakeholders, using tools such as Kanban boards, cumulative flow diagrams, or burn-up charts. By making WIP visible, we can see the current state of the work, identify bottlenecks, limit WIP to match capacity, and improve flow efficiency.  References :  Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths ,  Make Value Flow without Interruptions ,  SAFe Principle 6: Visualise and limit WIP, reduce batch sizes, and manage queued lengths

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, one of the core values of SAFe is alignment, which means that everyone involved in the solution development has a common understanding of the vision, strategy, and goals. To achieve alignment, teams need to demonstrate progress by showing the actual working product to the stakeholders and getting feedback. This is done through the sync events such as the Team Demo and the System Demo, where teams showcase the features and stories they have completed in the iteration or the PI. By showing the actual working product, teams can validate their assumptions, measure the value delivered, and identify improvement opportunities.  References :  Exam Study Guide: SP (6.0) - SAFe® Practitioner ,  SAFe® for Teams - Know Your Role on an Agile Team ,  SAFe for Teams | SAFe Practitioner (SP) Certification

The System Demo is a significant event that provides an integrated view of new features for the most recent iteration delivered by all the teams in the Agile Release Train (ART). Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI) and the opportunity to give feedback on the solution. The System Demo is the one real measure of value, velocity, and progress of the fully integrated work across all the teams. The purpose of the System Demo is to demonstrate new functionality, not to evaluate the full PI, introduce new architectural designs, or identify PI Objectives. Those activities are done in other events, such as the Inspect and Adapt, the Architectural Runway, and the PI Planning.  References :  System Demo ,  System Demo - Scaled Agile Framework ,  Why System Demo Considered A Significant Event In SAFe®? - Learnow ,  System Demo - Scaled Agile Framework .

This statement is one of the Lean budget Guardrails, which describe the policies and practices for budgeting, spending, and governance for a specific portfolio 1 .  Continuous Business Owner engagement means that the Business Owners, who are key stakeholders for each Agile Release Train (ART), are actively involved in the planning, execution, and review of the value delivery 1 .  They provide feedback, guidance, and approval for the PI objectives, features, and enablers, as well as participate in the Inspect and Adapt (I & A) workshop and the Program Increment (PI) system demo 2 .  Continuous Business Owner engagement helps ensure alignment, transparency, and accountability for the value streams and ARTs 1 .  References :  Lean Budget Guardrails ,  Business Owners