"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."
In a fit of rage caused by reading yet another email in which one of our customers proposed creating a "devops team" so as to "implement" devops, I tweeted that "THERE IS NO SUCH THING AS A DEVOPS TEAM." Like all slogans, there's plenty of heat to go with the light, so here's the scoop [...]
We wrote back in August about 3 "litmus test" questions about #DevOps in your organisation. We'd like to add 3 more questions that focus on the more operational aspects of DevOps.
This months talk from DevOps.Net's James Betteley, gives us an experience report on how easy it is to get it wrong when key individuals don't get "on message".
What's interesting is the differences in the behaviour and the language used by the teams who don't get it compared to the teams that do.
A great starting point for anyone interested in the state of automation on Windows, especially if you're coming from a lInux environment. Lots of snippets to get started with powershell, Chocolatey packages and winrm.
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.
