It’s said that ‘If You Can’t Measure It, You Can’t Manage It’. In any case, how would you quantify behaviour or mind-set? Therein lies the challenge with measuring DevOps. DevOps is about a mind-set – a culture that is comprised of procedures and practices that...
No, It’s nothing new. It existed in a primitive form in the old “green screen” days for 20+ years. Many early adopters attempted to apply automation to applications-under-development but found themselves spending more time developing and maintaining automated test scripts than they did manual testing.
In any DevOps transformation there are 3 key aspects which are directly related to agility which impact achieving business objectives. These are collaboration, process re-engineering and continuous skill enhancement and all of these aspects span multiple domains.
Sound familiar? As per the estimation, around half of enterprises are planning to initiate a continuous integration and continuous delivery (CI/CD) in the near future, but significantly fewer are making concrete steps towards it because of the scary leap from SysOps to DevOps.
Lets start with understanding business drivers in layman’s language and then deep dive in tech to understand DevOps DevOps is all about Time to market. Bringing incremental changes to production and experiment on a continuous basis to figure out what works and what doesn’t. In...
There are many books and blogs are written on DevOps. Some popular definitions are “DevOps is a process enhancement”, “it is a way organizations can implement cultural change”, “collaboration between IT and Operations” etc. In the world of everything as a service,
If you are still working in a traditional working environment, one would observe an application developer awareness of software development life cycle activities include standard phases: requirement gathering, analysis, design, coding, and testing (unit, integration, user and system).