Changing Culture to Enable DevOps
Changing tools is easy when compared to changing people and processes. How can we cultivate an organization’s culture to identify and solve DevOps problems?
Changing tools is easy when compared to changing people and processes. How can we cultivate an organization’s culture to identify and solve DevOps problems?

There are intangibles that result from adopting Agile development techniques. The hidden side of the transformation, so to speak – the changes in perceived values of interpersonal relationships, the enhanced necessity for trust, the soon-obvious need for enhancing cross-site communication inefficiencies are examined in this article.
Wanjun Zhuang asked the members of the LinkedIn Agile Coaching group about earning trust with his new Agile team. His team members consider him a manager and are not open with sharing because they consider him someone who is checking up on them. There has been a significant amount of diverse advice that is potentially very useful to any (software) team.
This is the first in a series of discussions looking at factors that enable teams to be successful. This post reports on a recent Wired magazine article that looks at the creative process in use at Pixar Animation Studios and how their process encourages team formation, long-term relationships and trust in a “safe to fail” environment.
There has been plenty of debate on what skills a developer needs, or what practices an organization must adopt for agile to be successful. But while undeniably important, is this really what's at the heart of agile success? Mark Schumann suggests that agile's "one essential ingredient" is not ground-level agile technique, but rather is the agile mindset within management ranks.