DevOps and Bimodal IT: myths & truths DEVOPS AND BIMODAL IT: MYTHS AND TRUTHS DevOps and Bimodal IT are two terms which have recently come onto the radar in the world of enterprise IT. Confusion surrounding the definition and use of these concepts is rife so we sought to demystify these terms and understand how analysts such as Gartner see them in play over the next few years. Eddy Pauwels, VP of Sales and Marketing at Clarive Software, were interviewed by Enterprise Management 360º a few days ago… “This is why I often speak about lean application and service delivery when an organization is serious about DevOps. I believe they should look at the following things; first of all, they should look at application delivery from an end-to-end or a holistic perspective and try to orchestrate it like this. It should try to automate whatever can be automated so that one can deliver at a speed of business and that can be ranging from a few times a year or frequently a few times a day or even an hour if really need be.” “I believe that DevOps is one of the key answers to support a Bimodal IT organization providing of course that it’s implemented properly and supported by the right infrastructure tooling. As we’ve seen DevOps improve the collaboration and communication between development and operations and try to increase the level of automation in order to support the delivery at the speed of business.” “A good DevOps tool or solution supporting Bimodal IT for me should at least have one of the following characteristics. Firstly, it should allow you to define and automate any discussion topic between development and operations, whether these are called releases, projects, springs, test cases, change requests or defects, you name it. Secondly, it should be able to provide you with dynamic end-to-end insight into status and activity within the delivery process regardless of the mode being used, so that you really get a deep understanding from a customer perspective inside the delivery process.” To listen to the full interview, please click here
CLARIVE @ DECODING DEVOPS IN BANGALORE CLARIVE @ DECODING DEVOPS IN BANGALORE During his session about Lean Application Delivery, Eddy Pauwels spoke about DevOps being very similar to marriage: You want to unite 2 distinct entities (Dev and Ops, or man and woman) into something that adds more value (DevOps, or “married couple”). As within marriage, this is a cultural/behavioral journey without an end; it requires constant investment and adaptation. Every married person knows that this can only happen if you can communicate/collaborate well with each other. (more…)
DevOps Broken Windows Broken windows is a criminology theory that says that if you let one window to be broken in an unoccupied building, more windows will be broken — as the building degrades, sooner or later a band of squatters will settle in. In a short time, the broken-into building becomes a hub where crime gravitates in the neighborhood. The theory suggests that, by tackling petty offences, police officers can effectively reduce citywide crime. But broken windows theory goes deeper that just patrolling officers and crime watching. It deals with changes in the cultural and social fabric of a community. It deals with social boundaries and how people adapt to the increasing diversion that starts with one seemly trivial incident such as a broken glass (or graffiti, littering, etc.). When a person walks by a broken window, perception of the surrounding changes. The domino effect starts with how a person reacts to the proliferation of rundown areas. Most avoid them. Some feel detached from that part of the community. Others join in and break more windows. (more…)