From b30434ba24d4400814d39655a0454d053fa253c8 Mon Sep 17 00:00:00 2001
From: ITkaleidoscope <67331837+Gielen1@users.noreply.github.com>
Date: Wed, 2 Oct 2024 17:18:50 +0100
Subject: [PATCH] Update index.html

Hi, as i was preparing for a session with a customer i decided to to talk to them about how there is no silver bullet and discuss diff 'models' and evolution. Ended up describing a HL model ill suggest...    thought that ill share this potential 'new' type as i think may be of use/work well alongside others? either way, will love thoughts.  I hope this the PR correctly though?!
---
 index.html | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/index.html b/index.html
index a6e5939..631b624 100644
--- a/index.html
+++ b/index.html
@@ -624,8 +624,28 @@ <h5><strong>Type 9:</strong> Dev and DBA Collaboration</h5>
                 </div>
             </div>
         </div>
+        </div>
+
+	        <div id="type-ten" class="row">
+        <div class="col-1-2">
+            <h5><strong>Type 10: Platform DevOps </strong> </h5>
+
+            <p> For organisations, usually large and complex with a fairly traditional IT Operations department, combined with some Dev, which cannot or will not change rapidly [enough] towards agile ways of working and the adoption of standard and recommended practices like Product Mgmt/Product-Led/Product Op Model, CI, iterative development etc, for the platform and the delivery of platform XaaS.These organizations are likely to have a large Ops hybrid model, perhaps with on-prem and multi-cloud. It probably helps to create the first iteration of  "DevOps within Platform Ops",  this looks very much like  Anti-Type E: Rebranded SysAdmin, but the intent and planned for objectives are VERY different. So, the plan does include 
+cultural/organizational change. Similar than in Type 5, it also intends to bring non platform Devs and Ops closer together, however the big differences are  'longevity' and responsibilities/scope. The team is there to stay, expand and evolve, to offer platform services  and then ideally move towards  Type 2 (Fully Shared Ops Responsibilities) -for the platform  or   Type 1 (Dev and Ops Collaboration) model. Ultimately, the desire is that following the design of a platform group with the right topology (ie: one for IaaS), the  platform group builds 'Dev' capabilities and standard and recommended practices, for their Platform. (ie: CI, Product led, Platform engineering etc) and at the same time closes the gap between their internal dev customers and their platform offerings. 
+</p>
         </div>
             
+        <div class="col-1-2">
+            <div class="spacer"></div>
+            <div class="suitability medium">
+                <i class="fa fa-check-circle"></i>
+                <div class="suitability-inner">
+                <p><strong>Type 10 suitability:</strong> precursor to type 1 or type 2 model, beware of of difference from model type 5 and anti-type E.<br/>
+        <strong>Potential effectiveness:</strong> <strong><span>MEDIUM to HIGH </span></strong></p>
+                </div>
+            </div>
+        </div>
+        </div>
         
     </div>
     </div>