Last updated on
Plutora Blog - IT Governance, Release Management

Here’s a Project that Demands Real Release Management Governance

Reading time 3 minutes

Release Risk and Release Management Governance

Continuous integration, continuous deployment pipelines, automated configuration and deployment tools such as Puppet and Chef all of these systems contribute to an IT department that understands that agility in software releases means more automation and finding smarter ways to manage risk without introducing needless process. But, what if you can’t just deploy to production.  While DevOps practitioners rail against needless corporate process introduced by ITSM and ITIL-focused approaches to IT management (or even the term IT management itself) the grassroots efforts to democratize access to infrastructure and deployment tools often runs straight into the wall of confusion when a project requires strict governance gates.

Build governance into engineering workflows with Plutora

Adapt governance to meet engineering teams where they are for continuous compliance and automatic auditability.

Learn More

On the one hand you want to enable developers, but what if your production environment is so sensitive and so risky that you need to have some way to translate between an innovative and unrestricted development group and a more controlled environment in production.  Plutora sees itself as just that adaptor. 

We provide a tool that manages the risky process of transitioning from development to production by providing a tool that can manage multiple governance gates. When you have 10-20 departments all releasing and innovating on their own schedules a tool like Plutora gives release managers a way to manage complexity and risk so that critical launch dates can be met wit integrity.

So, what kind of project needs release management governance gates?

Release Management Governance – While I was watching some of the coverage of the initial test flight of NASA’s Orion space capsule I saw just such an example of a project that requires strict, last-minute governance gates to “deploy” software.  Yes, I know that Orion is a spacecraft, but let’s admit that on several levels Orion is representative of a large software project.  In this case the software isn’t being deployed to The Cloud, it’s being launched into space.  Just what kind of governance gates are required for a final launch?

Orion Launch

Here watch this video:

Release Management Governance – Just in case you lost count that was 30 approvals before the launch director (maybe the ultimate example of a release manager) could give the final go-ahead for launch. What is the risk profile associated with launching failures into your Core Banking Platform, Investment Management System, Flight Booking System, Airline Passenger System, Telco Billing, Telco Customer On-Boarding, Patient Care Delivery, etc? How much transparency does your ‘mission-control’ have.

dalibor siroky
Dalibor Siroky

Dalibor is the Co-founder and Co-CEO of Plutora. He has 15 years of leadership, consulting, enterprise product, and operations experience across Australia, Asia and Europe. He has proven ability to build high performance teams, turn around situations, develop innovative products, and create lasting value. Prior to Plutora, Dalibor was founder and managing director of Finotaur, a leading provider of independent management consulting services. Before that he served as CIO of financial advisory software at Macquarie Bank, head of solution architecture at Commonwealth Bank of Australia, and management consultant at PricewaterhouseCoopers. Dalibor got his MBA from the University of Chicago Booth School of Business. Follow him on Twitter @DaliborSiroky.