Most enterprises approach DevOps adoption in a singular fashion: they use a bottom-up approach that is typically technology-driven and groups all considerations like, culture, metrics, processes and communication into a single stream of work that is often led and implemented solely by technology-oriented champions.
However, this singular approach presents a few issues:
(1) First, it leads to […]
The short answer is No; but let me explain why. DevOps as a movement is really about one simple thing: breaking down the silos between your IT functions – predominantly Development and Operations in the widest sense. Development here means development, business analysis and test, while Operations covers also some aspects of test, infrastructure and […]
DevOps is the original concept or philosophy that is the basis for everything “Continuous”. When DevOps was initially incepted, the simple goal of the philosophy is to breakdown the silos and barriers between the development and operations teams and establish trust between the two organisations to achieve the business benefits of better time to market, […]
The concept of technical debt is generally useful in approaching software development projects whether delivered internally or via a system integrator.
Technical debts are simply the amount of compromises to the code measured in the amount of work that needs to be done to fix these issues. Usually reflected in days and hours, if you multiply […]
