Agile Software Development

DevOps Revolution: Relevance, Principles, Best Practices

DevOps is a mixture of Agile and Lean principles that are used for IT software development. The differential factor is that the approach is more conducive to the modern business models and technological shifts. In his blog article, Henny Portman discusses how DevOps is relevant to the market, its principles, and best practices.

Understanding DevOps

The author has given an overview of Oleg Skrynnik’s “DevOps – A Business Perspective”. The book is one of the foundational courses of EXIN DevOps Foundation certification. Its 6 chapters deal with definition, challenges, principles, best practices, and case studies. The following paragraphs will talk about the relevance, principles, and best practices developed around DevOps:


  1. Reduction in time to market
  2. Lowering of technical debt
  3. Removing weak spots

The Five Principles:

  1. You must create value that customers would acknowledge.
  2. The deployment workflow should be automated from development to distribution.
  3. All versions of the development should be saved in a version control system. You can store source code, test cases, scripts, artifacts, libraries, documentation, configuration files, development software, etc.
  4. DevOps configuration management should be automated. To make changes to an environment, do so only through scripts stored in the version control system.
  5. DevOps’ definition of done depends on the working software model. A feature is successful and done if it works seamlessly in the production environment and testing, assembly, and deployment platforms.

10 Best Practices:

  1. Have a cross-functional, high-performing DevOps team that is dedicated, co-located, and self-motivated.
  2. Create visible workflows to allow clarity in task status, reduction in handovers, and prevention of work duplication. You can prioritize or hold progress of a deliverable as required.
  3. Limit work in progress based on team capacity to reduce challenges and expert interventions.
  4. Shorter batch sizes reduce the possibility of defects and boost quality deliveries.
  5. For a DevOps project, the product owner should have an IT system that fulfills functional and operational obligations.
  6. Testers should create a testing environment that resembles its production counterpart and detects bugs early.
  7. Mandate hours to improve processes with improvement projects like Kaizen Blitz and hackathons.
  8. Funding for DevOps projects should be based on the potential value of the business cases.
  9. Prioritize tasks based on the cost a delayed deliverable would incur on the project.
  10. Encourage continuous improvements.

To view the original article in full, visit the following link:

Show More
Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.