> [!tldr] Technical and business principles codified into a pithy document I like the project manifestos I've run across in the wild. [[Obsidian]], [[Archimate]], [[Agile]]. They tend to[^1] follow this form: > **Simple credo statement** > *rationale justifying why you the credo exists and you should adhere to it.* [[The Compass Metaphor]] comes to mind. This is a *scope-based compass*. It's sort of akin that "north star" that consultants always talk about. ## Examples > [!example] Obsidian > ### Durable > > We believe that your data should be future-proof and easily accessible, no matter where you are. That’s why we use simple, open file formats that prevent lock-in and ensure that your data can be preserved for generations to come. > [!example] ArchiMate > **Needs of the many over wants of the few** > Any change to the language shall cover a clearly identified and important use case of a substantial part of its users. In line with the previous principle, keeping things simple for the “80%” is more important than catering for the wants of the “20%”. > [!example] Agile > Working software is the primary measure of progress. **** # More ## Source - [[Archimate Manifesto]] - [[The Agile Manifesto]] - https://obsidian.md/about [^1]: but not always