Add org and practices

cchesser · Oct 24, 2021 · fc3b2f9 · fc3b2f9
1 parent 329f0d7
commit fc3b2f9
Show file tree

Hide file tree

Showing 4 changed files with 36 additions and 2 deletions.
diff --git a/content/Organization/_index.md b/content/Organization/_index.md
@@ -0,0 +1,15 @@
+---
+title: SADMF Organization
+description: Organizing for control
+weight: 2
+---
+
+## Organizational Command Structure
+
+### Source Management Team
+
+To improve coder productivity by reducing the work required for integrating changes, we introduce the Source Management Team. The SMT is responsbile for accepting the complete [feature branches](../practices/#fractal-based-development) from each coder and merging the changes into the Conflict Resolution branch. They will then resolve all conflicts for the coders before alerting the Quality Control team that the Convoy is ready for testing.
+
+### Quality Authority
+
+Verifying quality is a specialist field that no coder is qualified to perform. In addition, performing testing impedes the ability for the coder to do their job, write code. The Quality Authority team is the final arbiter of what the requirements mean and will create, maintain, and manually execute tests scripts based on their understanding of the requirements. The end-user uses the system manually, so that is the only TRUE way to test it!
diff --git a/content/Practices/_index.md b/content/Practices/_index.md
@@ -0,0 +1,19 @@
+---
+title: SADMF Practices
+description: Recommended practices
+weight: 2
+---
+
+### Fractal-based Development
+
+Below is a **simplified** version of the recommended branching pattern with permanent branches for Testing, Conflict Resolution, and Development. Each feature branch will exist for the duration of feature coding. All feature branches will branch from the clean `develop` branch. When notified, the [Source Management Team](../organization/#source-management-team) (SMT) will merge to the `conflict` branch to perform [Conflict Arbitrage](#conflict-arbitrage). Once the strongest changes are merged, SMT will notify the [Quality Authority](../organization/#quality-authority) who will pull the changes into the `test` branch for certification. Once the code has been certified, it is authorized for the next Release Convoy to set sail! This is the most effective branching pattern to enable [Continuous Isolation](https://continuousisolation.com/).
+
+![Fractal-based Development](../images/fractal-based-development.png)
+
+### Conflict Arbitrage
+
+When the Source Management Team has received all candidate changes for merging, they will merge all changes into the `conflict` branch and referee the conflicts. This ensures only the strongest changes survive!
+
+### CI/CD/ED
+
+Continuous Isolation / Continuous Deliberation /Eventual Delivery is the most effective way to ensure that we have the highest levels of process adherence, real-world manual testing, supporting documentation, executive sponsorship, and perfection for every change!
diff --git a/content/_index.md b/content/_index.md
@@ -1,10 +1,10 @@
 ---
-title: Scaled Agile DevOps Maturity Framework 2.3
+title: Scaled Agile DevOps Maturity Framework 2.4
 description: Making enterprises feel better about DevOps transformation since 2021
 weight: 1
 ---
 
-# Scaled Agile DevOps Maturity Framework 2.0
+# Scaled Agile DevOps Maturity Framework 2.4
 
 >**Enterprise transformation without the risk of culture change!**
 

diff --git a/static/images/fractal-based-development.png b/static/images/fractal-based-development.png