Summary of DevOps Days Kiel day 1 talks.
Tony Grout and Chris Matts spoke about the emerging areas of business mapping and skills liquidity at QCon London 2016 and how they apply them at Lloyds Bank. They showed how they deploy these techniques and explained how they combine business strategy with the abilities and aspirations of people to improve collaboration between business and technical stakeholders. InfoQ interviewed them.
AirFlow recently joined the Apache Incubator program. AirFlow is a workflow and scheduling system designed to manage data pipelines. Developed by AirBnb for their internal usage, it was open sourced last September, as previously reported by InfoQ.
In order to implement DevOps, individuals and organizations must prepare for the culture shift, new tools, and automation. This consensus has evolved during years of debate concerning what exactly DevOps means and how to use it. There are many voices in the discussion, and even with some areas of consensus, many points are far from agreement.
InfoQ interviewed John Willis about what made him decide to talk about burnout, the possible effects of burnout for a person, how burnouts are impacting the software development industry, leading indicators of a potential burnout and how they can be used to prevent burnouts, and suggestions for dealing with mismatches between employees and organizations that can cause a burnout.
InfoQ interviewed Martin Kearns about how agile contracts differ from contracts for waterfall projects, how contracts can deal with scope changes, major disturbances or delays during development, how contracts can enable agile behaviour and help all those involved to work together based on an agile mindset, and the role that lawyers can have when organizations want to use contracts with agile.
SAFe framework recently introduced the concepts of CapEx and OpEx concepts of Agile budgeting and capitalization.
In a recent blog post Henn Idan raised an issue that using Oracle Java in containers could be violating the Oracle licensing agreements. Is this an issue, or is it something that developers should be concerned about? InfoQ investigates.
An interview with Erin McManus and Ryan McKergow about the need for business analysis in agile, how agile impacts the role of the business analyst, the changes that they have seen in business analysis when agile is being adopted, and specific business analysis practices that that they can recommend for agile teams.
Andy Kelk talked about nurturing and growing agile teams at 1st Conference in Melbourne, Australia. His talk is based on the blog post Culture Gardening.
InfoQ interviewed Stephen Carver about how bringing in procedures and rules often doesn't help to prevent problems, enabling communication between engineers working in different companies, taking learnings from failure to a next level to prevent similar problems, and what engineers can do if they want to influence decisions on developing and releasing products.
Dan North gave a talk about business mapping at the Scaling Agile for the Enterprise 2016 congress in Brussels. InfoQ interviewed him about the problems that he sees from a business perspective when the IT part of an organization adopts agile, and asked him what business mapping is and how it can help organizations to increase their agility.
AutoScout24’s Journey to Microservices: Christian Deger on Transformation, Principles and Technology
At the Dublin Microservices User Group, Christian Deger presented “Highway to Heaven”, the AutoScout24 journey from deploying code into a monolithic application using a traditional IT development process, to utilising a microservice architecture with cross-functional teams. This technical and organisation transformation enabled the business to react more rapidly to changing market conditions.
InfoQ ran a DevOps research question during Q4 of 2015, to find out which practices contribute the most to a healthy DevOps culture. The results show there are no predominant practices as DevOps initiatives are highly contextual.
InfoQ spoke to Vasco Duarte on how the #NoEstimates technique may apply to a contracting environment, facing tipical needs of sizing a project, establishment of agreements, signature of contract and building of trust.