Differences

This shows you the differences between two versions of the page.

--- processes:safe [2024/03/24 18:20] – skipidar
+++ processes:safe [2024/03/24 18:39] (current) – skipidar
@@ Line 212: / Line 212: @@
 **2. Apply systems thinking**
-Deming observed that addressing the challenges in the workplace and the marketplace requires an understanding of the systems within which workers and users operate [2]. Such systems are complex, and they consist of many interrelated components. But optimizing a component does not optimize the system. To improve, everyone must understand the larger aim of the system. In SAFe, systems thinking is applied to the system under development, as well as to the organization that builds the system.
+Deming observed that addressing the challenges in the workplace and the marketplace requires an understanding of the systems within which workers and users operate
+Such systems are complex, and they consist of many interrelated **components**.
+But optimizing a component does not optimize the system. To improve, everyone must understand the larger aim of the system. In SAFe, systems thinking is applied to the system under development, as well as to the organization that builds the system.
+{{https://scaledagileframework.com/wp-content/uploads/2022/11/2-Apply_systems_thinking_F01.svg}}
+**The Solution is a System:** https://scaledagileframework.com/apply-systems-thinking/
+{{https://scaledagileframework.com/wp-content/uploads/2022/11/2-Apply_systems_thinking_Thumb_01-1.svg}}
+  * **Understanding System Boundaries:** Team members must clearly understand where a system starts and stops, how it interacts with its environment, and how it connects with other systems.
+  * **Suboptimization:** Optimizing a single component can be detrimental to the overall system's performance. Components can consume excessive resources, hindering other elements.
+  * **Holistic Understanding:**  For a system to function effectively, teams need to grasp the intended behavior and architecture, including how components collaborate to achieve the system's objective. Intentional design is crucial in systems thinking.
+  * **Value in Interconnections:** A system's value stems from its interconnectedness. Interfaces, along with the dependencies they create, are essential for delivering ultimate value. Continuous focus on these interfaces and interactions is paramount.
+  * **Integration Speed Limits System Evolution:** The speed of system development is constrained by its slowest integration point. Faster integration and evaluation cycles accelerate system knowledge growth.
+**The Enterprise is a System: ** https://scaledagileframework.com/apply-systems-thinking/
+{{https://scaledagileframework.com/wp-content/uploads/2022/11/2-Apply_systems_thinking_Thumb_02.svg}}
+  * Building complex systems is a social endeavor. Leaders must cultivate an environment where people collaborate on the best way to build better systems. Suppliers and customers are integral to the development value stream and must be treated as partners based on a long-term foundation of trust.
+  * Optimizing a component does not optimize the system. Optimizing local teams or functional departments does not enhance the flow of value through the enterprise. As with physical systems, the value of the system passes through its interfaces.
+  * Accelerating flow requires eliminating functional silos and creating cross-functional organizations, such as Agile Teams, Agile Release Trains (ARTs), and Solution Trains.
 **3. Assume variability; preserve options**