This is a complimentary comments set in support of the Code of DevOps Practice. Each statement of the Code is explainf in this document.
Code of DevOps Practice is an open proposal for organising creative work of DevOps in modern enterprise. The document includes: subject, cause, values, pillars and principles of the DevOps development as well as some best practice recommendations and a list of referred articles.
While DevOps have elevated delivery velocity to the level that only Sun is higher and made it the goal and work effectiveness criteria (regardless quality), they still claim they are agile. The article takes a look into Agile Manifesto and Scrum Guide for the role of velocity. Neither the Agile Manifesto nor the latest version of the Scrum Guide (2017) reveals velocity at all, but have many loopholes inherited by DevOps.
One of the major task of DevOps is a speedy delivery of Microservice into production. The major objective of QA and Testing is to find as many bugs as possible. Fixing these bugs slows down the delivery. The article describes this conflict in details, outlines problems in testing articulated by Mr Martin Fowler, proposes additional tests and explains how to improve quality of the released Microservices.
Article discusses issues with modern light-weight testing applied via automation in DevOps practice and states that such testing is not necessarily enough for quality products, especially in the case of distribution in Cloud.