1 of 11

DevOps Why its failing

2 of 11

Definitions

DevOps - a set of practices, tools, and a cultural philosophy that automate and integrate the processes between software development and IT teams. It emphasizes team empowerment, cross-team communication and collaboration, and technology automation.

DevSecOps - (short for development, security, and operations) a development practice that integrates security initiatives at every stage of the software development lifecycle to deliver robust and secure applications.

NetDevOps - a way to build network automation into the application development process, so that an application can understand the infrastructure needs and be programmed to create networking resources on demand.

Plus FinOps, SecOps, NetDevSecOps……..

3 of 11

4 of 11

The main reasons why “DevOps Fails”

  1. When it becomes about technology and not your people and adapting your culture.
  2. You don’t make the upfront effort to get it right.
  3. You’re still spending too much time fixing broken build, test or deployment pipelines.
  4. You don’t have the capability within your teams and still rely on goodwill. Your people are the most important part of this.
  5. You employ people with fancy job titles and do not understand if they are able to do the job.
  6. Your business hasn’t adapted over time……

5 of 11

Cloud & Businesses

Startup

Developer takes on the initial cloud work and, as the startup goes through funding cycles, they start to employ a Cloud Engineer, generally working in a small team. Max number is generally 2-3 engineers.

SMB

Will have 2-3 Cloud Engineers who work either in product teams or sit silo. They will have to take on many workloads. The max number is generally 4-5 engineers, dependant on how important the company feels about 'cloud’.

Enterprise

Will start off silo’d if introducing cloud for the first time before they transform or transition to cloud.

Year 1-3 of Transform/Transition - Will move to product teams with Cloud Engineers embedded. They will still have separate infrastructure team to manage legacy.

Year 3-5 Moved to Cloud - Will have mainly product teams with still some legacy left. Still a small legacy team, may have a cloud centre of excellence or may exist over different teams.

Year 5-7+ Embedded within Cloud - dependant on many factors they may still have legacy but now they have a large cloud presence, they may be mature or need a review.

6 of 11

Cloud Consulting:

  • Cloud Operating Model or Adoption Framework
  • DevOps Assessment
  • WoW / Training
  • Service Delivery
  • Cloud Centre of Excellence
  • Strategy and Roadmapping
  • Cloud Delivery

Job Roles in the Market

  • Cloud Consultant, DevOps Lead, FinOps

Cloud Architecture:

  • Architecting for the Cloud
  • Best Practices
  • Architecture Patterns
  • Standard solution architecture
  • Well architected frameworks

Job Roles in the Market

  • Cloud Architect, Cloud Lead, DevOps Lead, Platform Lead

Cloud Security:

  • Data Protection
  • Data Privacy
  • Threat/Vulnerability Modeling
  • Incident Response
  • Data, Legal, Regulatory Compliance
  • Security monitoring, Security Tooling

Job Roles in the Market

  • Security Engineer, SecOps Engineer, DevOps Engineer

Managed Service / Hosting

  • Monitoring
  • Configuration Management
  • Patching / Vulnerability Management
  • Compliance
  • Cost Management

Job Roles in the Market

  • Cloud Engineer, Cloud Support Engineer, Platform Support Engineer

Cloud Native:

  • Serverless, IAAS / PAAS /SAAS
  • CI/CD, Automation,
  • Orchestration/Container Platforms
  • Monitoring Applications, Observability
  • Infrastructure as Code

Job Roles in the Market

  • Serverless/Full Stack, Cloud Developer, DevOps Engineer

Cloud Engineering:

  • Build Landing Zone
  • Cloud infrastructure, IAAS / PAAS / SAAS
  • Networking
  • Logging, Monitoring Alerting, Observability
  • Migrations, Lift and Shift, Refactor
  • Infrastructure as Code

Job Roles in the Market

  • Cloud Engineer, DevOps Engineer, Platform Engineer

7 of 11

Putting Cloud into your organisation is not easy

8 of 11

Your biggest issue will be not having the right capability.

9 of 11

Main Skills for Cloud Engineer

AWS

Networking

DNS

VPN/

MPLS

Monitoring

Logging

Alerting

Terraform/

Cloudformation/ARM Templates/

Powershell

Puppet/

Chef/

Ansible

Jenkins/

Gitlab Pipelines/

CircleCI

Azure

GCP

Change Mgt

Problem Mgt

Incident Mgt

Data Compliance

Database Technologies

Storage

Data Compliance

Database Technologies

Storage

Cloud Provider Security

Pipeline Security

Security Operations

Architecture

Cloud Provider Best Practices

Cloud Consulting

FinOps

Optimisation

Sustainability

10 of 11

How Engineers start out in Cloud…

Skills

Year

Operate

Architect/Lead

Build

1

2

3

4

5

11 of 11

So how can you help…..