The term culture describes the processes and practices people use. And culture can only change when
people change the processes and practices they routinely employ. The introduction of distributed
version control system tools, such as Git, deployments with Docker instead of the use of monolithic
application servers, and the use of CI tools, such as Jenkins or Maven, in the software development
lifecycle will result in a culture change. But these changes are the result of the introduction of new
DevOps tools, not a prerequisite.
Any cultural change that DevOps precipitates is an output of using new tools and adopting new
processes. It is not an input.
It should be noted that many DevOps evangelists would take serious umbrage with this sample DevOps
interview question and answer. Be prepared to argue and defend both sides of the culture argument.