Skip to content

Update index.html #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Gielen1 wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Update index.html #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down