Rules - AME3

# The Rules of the (G)ame for Empirical-based Enterprise Evolution ![[AME3 Rules.svg]] [[AME3]] stands for **A**daptive **M**etaframework for **E**mpirical **E**nterprise **E**volution. The framework assists an enterprise in adopting a system design grounded in three [[The New New Enterprise Game|fundamental pillars]]: an [[Leadership|Agile Leadership System]], a [[Strategy|Strategy for Evolution]], and [[Rules|Enterprise-wide Rules]]. Adhering to the **AME3 Rules** enables companies to swiftly adapt their services & products to changing market conditions by using empirical evidence. Additionally, it fosters the simultaneous evolution of services & products with the organizational structure. [[AME3]] sets a minimal yet sufficient number of rules to allow integration with other frameworks and methodologies, ensuring clarity and reducing the likelihood of misunderstandings. It’s important to thoroughly understand the impact of these rules on the entire system before attempting to make any changes. The framework is designed primarily for small to medium-sized enterprises (SMEs). However, larger enterprises can also implement it within sufficiently autonomous divisions. While the [[AME3]] Rules alone are insufficient to enhance agility and effectiveness, enterprises must consider incorporating other methods and frameworks like [[Scrum]], [[LeSS]], LeSS Huge, [[Lean]], [[Kanban]], [[Wardley Mapping]], or [[Cynefin]]. The choice should align with the specific evolutionary stages of the product and organization and the particular [[Ambition|Ambitions]]. [[AME3]] is based on principles that align with these preferred frameworks and methods. In upcoming articles, detailed explanations of these principles and a comprehensive list of compatible frameworks will be discussed. Although some frameworks and methodologies may have different rules and recommendations, the combined use outweighs the inconsistencies. The **AME3 Rules** facilitate easy mapping and integration with other frameworks, enhancing overall effectiveness. A separate article will detail how to map these rules with different frameworks. --- ## Rules of the Arena ![[Arena]] ### 1. Leadership Functions ![[Team]] ![[Owner]] ![[System Lead]] ### 2. Artifacts ![[Improvement]] ![[Arena Backlog]] ![[Arena Product]] ### 3. Constraints ![[Match]] --- ## Rules of the Enterprise ![[Enterprise]] ### 1. Leadership Functions ![[Accountable Representative]] ![[Enterprise System Lead]] ![[Enterprise Owner]] ### 2. Artifact Artifacts on [[Enterprise]] level creating the transparency and data to lead the [[Enterprise]]. They connect the [[Enterprise]] with the [[Arena|Arenas]] and these with each other if necessary. All Artifacts of the [[Arena|Arenas]] are transparent and accessible to the [[Enterprise]] too. ![[Ambition]] ![[Goal]] ![[Enterprise Backlog]] ![[Enterprise Product]] ### 3. Constraints ![[Tournament]] --- ## Postscript The **AME3 Rules** intentionally do not delve into the reasons behind the rules, their functionality, or specific usage instructions. Detailed explanations and guidance will be addressed on [ame3.info](http://ame3.info). Here, however, are some foundational thoughts and motivations for the rules: Many organizations face challenges when implementing frameworks and methods such as [[Scrum]], Large Scale Scrum ([[LeSS]]), [[Lean]], and [[Kanban]]. A commonly cited issue is the lack of comprehensive organizational support. The [[AME3]] rules are designed to address this by providing just enough structural support within the enterprise to allow these frameworks and methods to thrive. Applying the **AME3 rules** can be considered a radical shift for most companies because it typically requires significant restructuring. For new enterprises, adopting [[AME3]] from the start is relatively straightforward. However, existing companies may need to navigate complex pathways and undertake major restructuring efforts at varying intervals. The **GAME3 rules** are designed to help identify necessary organizational changes. Future guidelines will offer strategies to concurrently reshape products, services, and organizational structures. [[AME3]] is distinct from Agile and Lean methodologies like [[Scrum]] or [[Kanban]] and is not intended to replace these or others developed over the past 30 years. Instead, [[AME3]] aims to enhance the benefits of these established frameworks and methodologies across the entire enterprise. Unlike the prescriptive nature of frameworks such as [[SAFe]], [[AME3]] allows organizations the flexibility to continuously adapt their structures and processes to meet the demands of a competitive environment. It is important to note that [[AME3]] is therefore incompatible with [[SAFe]] but offers a pathway to eliminate inefficiencies that may have been introduced by adopting [[SAFe]]. The Agile frameworks and methods recommended within [[AME3]] are defined with varying levels of precision, are subject to different interpretations by their authors, and may occasionally conflict in detail. Therefore, it is not possible for the AME3 framework to be fully consistent with all aspects of these varied frameworks and methods. In cases of discrepancy, the principles of inspection and adaptation are invaluable, which is a [[1. Empirical Control|Strategic Doctrine]] in GAME3. However, there is a certain beauty in this imperfection at the definitional level, which ultimately serves the creative and dynamic nature of human work. This approach recognizes that creativity needs contradictions, just as air is necessary to breathe. >[!button] [[Strategy|Continue reading]]  --- Version: Draft 9.3 / This work © 2024 by Peter Beck, Andreas Schliep is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/?ref=chooser-v1)