The Infrastructure Philharmonic: How Out of Tune are Your Operations?

It’s all too common for IT organizations to become compartmentalized. Each segment of the organization develops tunnel vision around their particular tasks and biases around their own tooling. For today’s fast-paced web businesses, the inability to effectively orchestrate all of it’s increasingly dynamic parts leads to slow and unreliable operations.

This presentation will examine, through examples of actual high performing organizations, what “well orchestrated operations” means and what it takes to achieve. We’ll examine both the cultural and tooling requirements as well as the necessary measurements for success.

Outline:

1. What do we mean by “orchestration” -The Philharmonic example (good) -The IT examples (bad)

2. What exactly are the boundaries of “Operations”? -Rolls up to a single business process spanning all the way from requirements to production -“Hey everyone, we are on the same team!” (and all supporting the same business)

3. Set a culture of orchestration: “You can’t incentivize what you can’t measure” -Examples of how poor performing companies improperly measure performance and disincentivize well orchestrated operations -Examples of how high performing companies measure performance in order to incentivize well orchestrated operations

4. Tooling and automation brings orchestration to life -Examples of how high performing companies use tooling to achieve orchestration, including (with emphasis on the integration between the tools): -Requirements traceability -Build Automation -Automated Provisioning -Configuration Management -Test Automation -Monitoring

5. A survey of current trends that are promoting orchestration: -DevOps -Agile Operations -Infrastructure as Code -ITSM monitoring -Test-Driven Operations -Continuous Deployment