This image has an empty alt attribute; its file name is DevOps-Lifecycle-1024x547.png
DevOps End-to-End Lifecycle

The DevOps (development working with operations) movement which began in 2009 was driven by the misalignment between agile software teams and non-agile operational teams. DevOps introduced 1 common goal ‘to put working software into production faster’, 5 new values and 3 new principles, known as ‘The Three Ways’.

DevOps is an end-to-end IT software development and delivery process that aims to shorten the software development life cycle and provide continuous delivery of high-quality software.

The goal of DevOps is to: Put working code (Dev) into production (Ops) faster

DevOps practitioners support this goal by automating and monitoring the process of software integration, testing, deployment, and infrastructure changes by establishing a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably.

High-Velocity IT is an umbrella term, that includes DevOps and Agile Software Development practices.  However, High-Velocity IT is much broader in scope, as it includes non-software development/delivery tasks such as Desktop, File Storage, Networking, Monitoring, Security, Support and many others.

The benefits of DevOps

  • Faster time-to-market (for software)
  • Shorter lead time between requests
  • Faster mean time to recover
  • Lower deployment risk
  • Higher deployment success rates
  • Caused a convergence within IT (Dev and Ops working together on a common goal)

The limitation of DevOps

  • Is designed for an IT department
  • Organisations may over-emphasise the importance of automation (tools) over culture (people)
  • Requires a specific software architecture i.e. microservices
  • Does not align the whole of IT (i.e. not all IT functions are involved with building and deploying software)
  • Shifts the bottleneck of work from IT to the Business