Ben Saunders - Client Principal at Contino, shares his insights on leveraging DevOps to avoid a Shakespearean tragedy when treating the cloud like a traditional data centre.

1. Enterprise DevOps - “To Be or Not To Be”...
How embracing automation and cross functional delivery teams will maximise
your Cloud adoption, whilst helping to avoid a transformation tragedy of
Shakespearean consequence!
Presented by:
Ben Saunders - Client Principal
ben.saunders@contino.io

2. Management Summary
Making the Inevitable, the new Standard
> Cloud Tragedy: Treating the cloud like a traditional data centre is a tragedy of
Shakespearean proportions - meaning that you miss out on many of the cost,
agility and time to market benefits.
> Optimal DevOps: The optimal model for cloud consumption is what we refer to
as Enterprise DevOps - small cross functional teams consuming the cloud
through automation and cloud native approaches.
> Baked In Compliance: When you bake in controls and compliance, your teams
can move quickly - without exposing your organisation to compliance, governance
or security risk.
> In this presentation, we will explain the Enterprise DevOps model, and explain
why it’s the optimal way to set up your cloud operating model.
Tweets: @Ben_DevOps

3. Lift and Shift - How Not to Get to the Cloud
Making the Inevitable, the new Standard
Wakey-Wakey: Enterprise organisations are waking up to the
opportunities that Cloud can provide to their businesses, by
way of innovation and market differentiation.
Same Old Mistake: However, many make the simple mistake in
assuming that by lifting and shifting their applications into the
Cloud, that the transformation journey is complete.
Maximal Value: To truly demonstrate the value of Cloud,
organisations must streamline business processes and
breakdown hierarchical team structures, which introduce
bureaucracy and lengthy software delivery lifecycles. Whilst
investment in tooling and education, is essential to ensuring
success.
This is where Enterprise DevOps can help….
Lifting and shifting, prevents
Cloud Native capabilities and
can stifle innovation.
Tweets: @Ben_DevOps

4. Enterprise DevOps - In A Nutshell
> Enterprise DevOps can be loosely defined as the
application of DevOps values and behaviors in an
environment that contains any of the following:
> Many interdependent and related systems and
subsystems.
> Software and teams that rely on each other.
> Monolithic systems and/or static software/hardware
environments.
> Loosely coupled and siloed application architectures.
> Antiquated annual/semi/quarterly release cycles.
Your Cloud Transformation without
DevOps…
Your Cloud Transformation with
DevOps...
Tweets: @Ben_DevOps

5. Enterprise DevOps and the Onset of Fear - Embracing Change
> “I am automating myself out the job!”
> “You can’t do that, because it breaches our internal
security standards!”
> “This transformation will cost us Millions!”
> “We need to demonstrate this data back to the
regulator, as a result we need to fill in this document…”
> “That is handled by our SI and its the way we have
always done it”
The fear of change is a major barrier to industrialised Enterprise DevOps for many organisations. Self preservation and hiding
behind security and compliance are often key blockers. Not any more!
“Fear leads to anger. Anger leads to
hate. Hate leads to suffering!”
Yoda - The Phantom Menace, 1999
I tried to find a Shakespeare quote
about fear...this one was better!
Tweets: @Ben_DevOps

6. Enterprise DevOps - Automated Compliance and Assurance
By empowering your resources with greater accountability, tooling and technology can be used to enhance visibility of software
interactions at each stage of the SDLC, ensuring controlled and compliant delivery with approval gates.
Data Masking & Virtualisation
Secure CI-CD Pipeline Controls
Infrastructure As Code and Continuous
Compliance
Containerisation
Metrics & Visibility
Tweets: @Ben_DevOps

7. Enterprise DevOps - Team Structures
DevOps tools alone will not assure your Cloud transformation, is fully successful. You should also consider re-structuring your
application teams to establish cross functional, co-located capabilities where possible. The concept of Product Squads can help
in this scenario, supported by Subject Matter Expert Centre’s of Excellence.
Example DevOps Organisation Structure
Each Product Squad should consist of automation skillsets to
integrate the security, compliance and traceability capabilities into
the delivery pipeline. A product owner is assigned and they work
closely with the business, akin to Agile delivery practices.
Specialist, niche skillsets are aligned to Product Squads, that have
alignment to specific applications from Dev to Production. SME
capability and additional delivery governance is provided by
Centre’s of Excellence, who define standards and governance
mechanisms that enable faster automated delivery.
Making the Inevitable, the new Standard
Tweets: @Ben_DevOps

8. Applying DevOps to Reach Controlled Continuous Delivery
Making the Inevitable, the new Standard
Leading digital companies are operating under a DevOps operating model – ‘You Build It, You Run It.’ Fortunately, these practices are now
also viable for large established enterprises in regulated industries as the tools, practices and approaches are proven.
DevOps teams operate in a more cross functional way and have more control of their stack federated to them, their use of automation
tooling will lead to more tightly controlled and audited environments and increased levels of quality and resilience.
Build Unit Test
Integration
Test
Dev
Deploy
Test
Deploy
Prod
Deploy
Continuous integration or release
automation tooling implements
role based access control...
Infrastructure, middleware and
application deployments are
repeatable using infrastructure as
code...
Automated approval and deployment
gates incorporated into the pipeline
here….
Incorporate DevSecOps security
scanning mechanisms here...
Tweets: @Ben_DevOps

9. Lighthouse Projects - How to execute Enterprise DevOps in the Cloud
Making the Inevitable, the new Standard
To accelerate technology and application innovation, whilst also remaining compliant and controlled, we have established the
premise of “Lighthouse projects”, which serve as a core underpinning in how we transform enterprise customers to embrace
DevOps in the Cloud.
A Contino Lighthouse project is an opinionated co-delivered
project using DevOps tools and agile ways of working. They span
legacy and greenfield digital systems and are designed to both
deliver tangible business value and a highly visible, replicable
delivery model which can be deployed to other areas of the
organisation.
Tweets: @Ben_DevOps

10. Closing Thoughts….
Making the Inevitable, the new Standard
> Baked In Compliance: We have discussed how DevOps in the Cloud can
accelerate time to market, increase regulatory transparency and ensure
security by baking controls into the delivery pipeline. Hence, assuring
predictable same way, every time delivery.
> Cross Functional Team: By shifting towards cross-functional teams,
organisations can enable enhanced end to end traceability. Whilst automation
allows a shift of focus from mundane maintenance, to breakneck innovation.
> Lift and Shift - No, No, No, No: Simply lifting and shifting applications into the
Cloud, will not bring maximum ROI as some applications are licensed in ways
which would make the Cloud counterproductive.
> People Empowerment: Technology is an enabler, however your organisation
needs to ensure that they enable your people with accountable empowerment,
by removing bureaucracy, moving away from policing controls and focusing
more on quality targets.
Your journey to Cloud
prosperity, needs to be
powered by DevOps.
Tweets: @Ben_DevOps

11. contino.io info@contino.io
@ContinoHQ
@ContinoHQ
Contino
Thank You!
London
1 Fore Street,
Moorgate,
London,
EC2Y 9DT,
UK
New York
404 5th Avenue,
New York, NY,
10018EC2Y 9DT,
UK
Melbourne
Level 2,
Hub Southern Cross,
696 Bourke St,
Melbourne VIC 3000,
Australia
— — —london@contino.io newyork@contino.io melbourne@contino.io