Discover the change management practices that are ripe for optimization
DevOps
Change has become the most important part of modern digital product cr ...
Read MoreThis post is from the XebiaLabs blog and has not been updated since the original publish date.
Back in April of this year, I had the honor of participating in the DevOps Enterprise Forum, hosted by Gene Kim and the IT Revolution team. The three-day event in Portland, Oregon gathered many of the world’s DevOps thought leaders to address obstacles impacting the DevOps movement and develop guidance to assist the DevOps community at large.
One of the biggest challenges of DevOps, especially in heavily regulated industries, is figuring out how to best integrate auditing best practices and guidelines into application development delivery processes -- without compromising velocity or quality. To address this challenge head on, I joined a team of respected DevOps industry individuals at the event, including Ben Grinnell, James Wickett, Jennifer Brady, Sam Guckenheimer, Scott Nasello, and Tapabra Pal. The team’s goal was to work with the Audit community to determine the best methods for addressing the audit-specific challenges associated with software releases and to create some initial guidance for the DevOps community to follow and build on. To extend an olive branch to the Audit community, the team penned an open letter titled, “Love Letter to the Auditor.” Supported by open source guidance, the letter is ultimately intended to help the DevOps community understand the controls they need to put in place and the risks they need to address in order to develop effective code.