About Compliance at Velocity

Chef
Compliance at Velocity

--

What will we discuss on this site, who is involved and why should you keep coming back?

First, a few words on Compliance

Regulatory compliance is a fact of life for every enterprise. At the same time, competitive pressures are increasing. Is it possible for industries to deliver new products and services at high velocity while still satisfying their obligations for regulatory compliance?

The answer is “Yes!” when you integrate compliance into a high-velocity DevOps workflow, with a focus on automation and highly connected, multidisciplinary agile teams.

This site collects thought-pieces from the frontline of building high velocity highly compliant enterprises.

This site isnt about a product or a tool. It is about a way of working. It is curated by Justin Arbuckle, an executive at CHEF Software and enterprise change-agent, and Jason Bloomberg an experienced technology commentator.

We believe the following things:

Technology outpaces regulation. Technology evolves faster than both regulation and its assessment, and auditor capabilities evolve over time. Ultimately, a person makes the call, not a compliance framework.

Compliance can’t wait. The decision to implement a low-level standards framework is more important than the choice of the framework itself.

Velocity matters. Improvements in small iterations, consistently applied, are preferable to ambitious, high-risk rollouts of large-scale compliance implementations with long lead times. Full and immediate compliance is impossible. Narrow, consistent efforts to improve compliance are better than illusory full compliance.

It has to be testable. Rules that are not testable can neither be consistently nor verifiably implemented. Tests provide a single, formal common reference point for translating requirements into implementation instructions.

Compliance without automation is fiction. In order to be highly compliant, you need to operate at high velocity. In order to operate at high velocity, you need to automate compliance.

Two speed IT must become high speed IT. Legacy application transformation is curtailed by compliance and technical debt. High velocity compliance is a mechanism for achieving legacy transformation.

If you believe the same things, or if you really really don’t, please come back and engage in the coversation with us.

--

--

Chef
Compliance at Velocity

The automation platform for DevOps and the high-velocity business // www.chef.io // @chef