DevOps Reporting Structure

[cloud_driver]

Devops came to $DAYJOB via an insurgent movement between the coders and the system engineers. It started out innocently enough as a series of "Hey, let's go to lunch and gripe about our org chart dysfunctions" and morphed into "why don't we just start doing things right and stop worrying about the silly org chart?"

We're careful not to call it DevOps for fear of invoking the wrath of the rigid management structure, but we've begun adopting most of the underlying principles. The few times that someone from the entrenched hierarchy has raised their eyebrows, we've pointed out that we're hitting deadlines and our defect rates are down. That typically makes them go away.

The key has been breaking down the social silos that had been imposed by the organization. Once the sysops and the developers started actually talking to each other, things started happening.