The DevOps Lifecycle: Keep C.A.L.M. and Carry On

Once upon a time there were two teams in charge of creating great software: Dev and Ops. Though they worked on the same product, their goals were diametrically opposed to each other. On one hand there was the Dev team pushing for feature changes, and on the other hand was the Ops team striving for stability.

Since the advent of the personal computer in the 80’s these teams have been siloed and burdened with dysfunctional communication during a product lifecycle that has historically led to delays and broken code. It was a sad tale to tell to end users everywhere.

Today, things have changed, radically. An entire movement was formed by new technology like cloud infrastructure and virtual machines. This cultural change in perspective combines the two teams into one lean mean rapid deployment machine, leveraging code to manage the infrastructure. It is called DevOps.

Transparency, collaboration and cross-functional teams with polyglot skills are breaking down the walls with automation and rapid deployment. Software gets shipped quickly, more often, code failures are detected and corrected faster and the product runs smoother. This sped up process allows innovation to flourish and companies to do more in less time.

“But,” you might ask, “how is the DevOps Lifecycle different?” It can be summed up with the acronym C.A.L.M.S.

  • C – Culture
  • A – Automation
  • L – Lean
  • M – Measurement
  • S – Sharing


The traditional software development lifecycle follows a Waterfall methodology that eventually morphed into the Agile SCRUM lifecycle. But for most enterprises the current lifecycle resembles something like an Agile-SCRUM-Fall.

The DevOps Lifecycle Looks Like This:

  1. Check in code
  2. Pull code changes for build
  3. Run tests (continuous integration server to generate builds & arrange releases): Test individual models, run integration tests, and run user acceptance tests.
  4. Store artifacts and build repository (repository for storing artifacts, results & releases)
  5. Deploy and release (release automation product to deploy apps)
  6. Configure environment
  7. Update databases
  8. Update apps
  9. Push to users – who receive tested app updates frequently and without interruption
  10. Application & Network Performance Monitoring (preventive safeguard)
  11. Rinse and repeat

The DevOps Lifecycle = A Rapid Release Cycle with a Strong Feedback Loop

Rapid Release Cycle with Strong Feedback Loop

Utilizing a DevOps lifecycle, products can be continuously deployed in a feedback loop through:

  • Infrastructure Automation
  • Configuration Management
  • Deployment Automation
  • Infrastructure Monitoring
  • Log Management
  • Application & Performance Management

To learn more about DevOps tools, visit our DevOps Tools Glossary.

What are your thoughts? Let us know!

Free E-book

Breaking down barriers and reducing cycle times with DevOps and continuous delivery

Learn how companies like Amazon, Etsy, Facebook and many others deliver new features faster, sometimes several times per day, while other companies wait months to release software updates.

Get the eBook

GigaOm Download

Free E-book

5 Unsung Tools of DevOps

Jonathon Thurman shares his five favorite DevOps tools which have been around a long time. They may not be flashy but they’re time tested and just work.

Get the eBook

5 Unsung Tools of DevOps cover

These are the top 10 snapshot results. To see complete query results, hit 'Return'.