Group items tagged

Interview with Patrick Debois

DevOps is een reactie op de onderlinge afhankelijkheid van software development (Dev) en operations (Ops). De spreekwoordelijke muurtjes tussen de Dev en Ops afdeling bestaan niet meer binnen DevOps. De implementatie van DevOps resulteert in een versnelling van de ' time to market' en een verhoging van de kwaliteit van delivery. DevOps gaat een stap verder in de richting die met Agile werken al is ingezet. Waar bij Agile werken frequent werkende software met de meeste toegevoegde waarde wordt opgeleverd, gaat DevOps nog een stap verder door de applicatie delivery te versnellen.

By John Willis

"Sinds de dagen van de zogeheten watervalsoftwareontwikkeling hebben IT-organisaties met Agile-methoden zoals Scrum al veel gewonnen aan snelheid en flexibiliteit. Gebruikers sturen voortdurend op de door henzelf gewenste functionaliteit en zien die snel terug in productierijpe projectresultaten. Hoe zorgt u er echter vervolgens voor dat die gebruikers ook snel kunnen beschikken over die in productie genomen functionaliteit? DevOps is het antwoord om projectresultaten snel in productie te nemen en tegelijkertijd de impact en frequentie van incidenten te beperken."

DevOps is a very successful meme in our industry. Most organizations these days seem to be saying that they aspire to it, though they don't necessarily know what it is.

DevOps isn't just about Dev and Ops. It's about corporate management as a whole.

Community Interactions in DevOps

DevOps Days has celebrated 5 years since the initial conference in Ghent in 2009. With events in Helsinki, Vancouver and Tel Aviv just in the month of November, the DevOps Days series has taken place across multiple cities all over the world in these 5 years. InfoQ talked to Patrick Debois and Kris Buytaert, part of the team that organized the first event 5 years ago.

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

This checklist is comprised of 48 items you can use to gauge the maturity of your software delivery competency, and form a baseline to measure your future improvements. It's not meant to say "you're failing DevOps" or deprive you of a badge (make yourself a badge just for reading this!), but surface areas of potential improvement.

A good write-up of an open spaces session at Devopsdays Berlin about the simplest ways of getting started with devops practices. Some good tips for anyone thinking about starting something.

What follows is a countdown of the people whom, if you pay attention to today, will supply you with practical knowledge, wisdom even, that you can put to work in the real world of IT as early as tomorrow.

Arrested DevOps is hosted by Matt Stratton, Trevor Hess, and Bridget Kromhout. ADO is the podcast that helps you achieve understanding, develop good practices, and operate your team and business for maximum DevOps awesomeness.