Avishai Ish-Shalom talked about the importance of moving from agile cargo cult to agile organizations at DevOps Days Ljubljana 2015. He gives some practical examples and guidance for taking full advantage of Conway's Law.
DevOps Days Ljubljana 2015 took place on the 3rd and 4th April and talks covered the full CAMS spectrum: Culture, Automation, Measurement and Sharing.
Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.
Rodoljub Petrović shares his lessons learned from growing engineering teams for years. If you want to change your organization's culture, take care of your hiring process and give it top priority. And follow these lessons.
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.
Brian Troutwine presented about complex and real-time systems at DevOps Days Belgium, covering interactions between humans and machines, with examples of automation done right and wrong.
DevOps Days is being held in Ghent, Belgium, October 27 and 28, celebrating 5 years since the initial one in 2009. After the first day, this second day included talks by David Zwieback, Dave Mangot, and Brian Troutwine, as well as lightning talks and open spaces.
DevOps Days is being held in Ghent, Belgium, October 27 and 28, celebrating 5 years since the initial one, also in Ghent, in 2009. These conferences have popularized the term DevOps, whose use has been growing since, with over 400 people attending, up from the 60 in the original one 5 years ago.
Lindsay Holmwood made a retrospective about metrics and monitoring in his DevOps Days Belgium talk, listed his typical metrics and monitoring pipeline, exposed some flaws in monitoring systems, and his view of what the future may bring in the field.
Jan-Joost Bouwman and Mark Heistek, from ING Retail Banking Netherlands, presented at Devopsdays Amsterdam how a CMMI-ITIL organization transitioned to a more agile mindset. Somewhat unusually in this kind of sessions, ING presented quantitative evidence of the improvements, such as a marked increase in the number of changes deployed to production and a decrease of the risk value per change.
At DevOpsDays Amsterdam, Mark Coleman asserted that all organizational's cultural changes start with one person influencing another. He finds that Charles Handy's writings on power and influence help on understanding how an organizations works and how one can go on to change it. Mark discussed Charles Handy's six sources of power and six methods of influence.
John Willis, one of the leading lights of the DevOps community, addressed the "State Of The 'DevOps' Union" at DevOpsDays Amsterdam. He started by mentioning the findings of the 2014 State of DevOps Report, went on to discuss Software Defined Everything and asserted that the future will be built around "consumable composable infrastructure".
On the first day of DevOpsDays Amsterdam 2014, bol.com, an online store, reported its experiences in its DevOps journey. Full automation, careful team building and an agile mindset that cross-cuts the organisation were the keys to success. RunDeck, Puppet, Hiera and Nagios enable bol.com to build and monitor a full working environment in under two hours, in a fully automated fashion.
Doug Barth, from PagerDuty, talked at DevOps Days London about their approach to start resiliency testing their systems without dedicating a lot of automation effort upfront. The goal was to quickly start learning about failure points and openly discuss how to fix them with only one hour per week of effort.
Frank Breedijk, security officer at Schuberg Philis, talks about the friction points between security and DevOps and how to collaborate to avoid them. Examples include automating security tests and environments, reducing scope of security audits to relevant system components only or allowing security fixes to jump the queue of changes to production.