A DevOps Manifesto created for Dominion Hosting Services, the datacenter for Dominion Enterprises.

1.
DHS DevOps Manifesto
Authored by
Matthew Tiffany
Empathy:
Understanding the needs of our customers
Empathy means understanding the how and why our customers do things. Once we
understand our customers’ needs, we can help them to work more efficiently.
Communication:
Form a relationship between Ops and Dev teams
Communication is how you form empathy. DHS will open lines of communications with
the development teams of the different businesses. Communication will be frequent and
ongoing to develop and maintain empathy between Ops and Dev teams.
Empowerment:
Implement a self­service infrastructure for development teams
DHS will empower the development teams. We will provide tools and knowledge so that
the development teams can deploy products with speed and quality. These tools will be
self­service and not require interaction with DHS.
Accountability:
Development teams are accountable for their own systems
Once the development teams are empowered, they must hold themselves accountable
for their own systems. They will be responsible for maintaining and updating their
systems and applications. DHS will be accountable for the underlying private and cloud
infrastructures and the tools for interacting with them.

2. Inform:
Provide dashboards for our customers
To hold the development teams accountable, we must provide them with useful
information. We will inform them of any problems they might be creating. We must also
let them know when they are doing things right. This information should be easy to
access and automatically generated through a centralized dashboard.
Trust:
Trust development teams with our systems
Empowering and holding the development teams accountable means trusting them to
access and use our systems without our direct control. We must trust but also verify.
APIs:
Resources are controlled via APIs
We must provide our customers with APIs for accessing our systems that verify proper
use. This will allow us to maintain a level of control.
Automation:
Automate everything
Automation over documentation
Everything will be automated. We will not have to update machines one at a time. We
will be able to auto deploy updates from a central location. Our systems will strive to
expand and shrink themselves and inform us whether they are working properly.
Infrastructure as Code:
Build continuous delivery pipelines for infrastructure
Updates go through a pipeline
Infrastructure as code is the means to automation. Servers will be deployed with a
configuration file, and updated when that configuration file is updated. We deploy
templates and configurations, not virtual machines.

3. LEAN:
Utilize continuous learning through LEAN practices
​Discover Problems
Predict: What’s going to happen?
Test: What really happened?
Solve Problems
Explain: Why was our prediction wrong?
Adjust: Make changes.
Reiterate: Do it better!
Spread Discovery
Teach and learn what was discovered
spread the information
Lead
Build a culture around doing the above.
Edited by
Guillermo Fisher
Jason Carpenter
Crystal Tiffany
Lucas Tiffany