Welcome!

@DevOpsSummit Authors: Zakia Bouachraoui, Pat Romanski, Liz McMillan, Elizabeth White, Yeshim Deniz

Related Topics: @DevOpsSummit, Java IoT, Microservices Expo, Linux Containers, Open Source Cloud, Containers Expo Blog, FinTech Journal

@DevOpsSummit: Blog Feed Post

Release Management By @DaliborSiroky | @DevOpsSummit [#DevOps #CMM]

Observations Across Industries: The Norm in Regressive

Assessing Your Maturity: Plutora’s CMM for Release Management

The Capability Maturity Model (CMM) has become an essential tool for assessing IT initiatives.  Originally developed to assess the capabilities of government subcontractors in the 1990s, the CMM is now used by IT management to define best practices in a particular practice area.  From Application Development to Database Management every practice in the IT department can be ranked against these models.

A CMM for a particular initiative will have a series of disciplines matched with a series of practices defining relative maturity.  For example,

  • A department that has well-documented deployments to production, a team of cross-trained release engineers, and post-implementation reviews for deployment activities is said to be at the highest level of maturity - Level 5 or Optimizing.
  • A department that reliant on individual, late-night heroics when performing undocumented deployments is said to be at the lowest level of maturity - Level 1 or Regressive.

Between these grades is Repeatable, Consistent, and Quantitative. Within a department you might be Consistent in Release Management and Regressive in Environment Management.  CMMs are not KPIs they are at a higher level and they provide a more subjective measure of performance.

Plutora's CMM for for Release Management

We've used our experience with Release Management (RM) and Environment Management (EM) across all industries and at the largest scales to define a CMM for RM and EM providing a set of questions our customers can use to assess their own maturity. We've also created the tool you'll need to start measuring and assessing your department's performance.

Plutora has broken down Release, Environments, and Deployments into Stakeholder Management, Release Management, Environment Management, Deployment Management, and Reporting, and we've provide processes and practices to illustrate levels of maturity for each discipline.

Screen Shot 2015 03 01 at 4.11.18 PM

Capability Maturity Model for Release Management and Environment Management

Regressive organizations are characterized by individual heroics and reliance on undocumented process and optimizing organizations are organization with automated, will-measured processes undergoing constant optimization.

In the Matrix shown above we identified characters or processes, which are associated with each level of maturity in our five disciplines. We've also identified five key opportunities for organizations to upgrade each discipline.

Observations Across Industries: The Norm in Regressive

I've seen a lot of release process, and I've seen a large number of companies managing environments, and the observation I come away with is that many of the release processes and deployment procedures in the wild are Repeatable and Consistent at best and Regressive at worst.

Most organizations (especially those that have moved into DevOps without a good strategy) are still heavily reliant on individual heroics to successfully manage environments and complete releases.  Many organizations have embraced automation for new applications, but have failed to migrate existing applications to modern approaches automated deployment.  Every organization we speak to without Plutora installed tends to lack stakeholder engagement or reporting solutions related to environments and releases.

Five Immediate Opportunities for Improvement

In our CMM we've identified five immediate opportunities for improvement:

  1. Value-based release reporting based on Director portfolios.  This is one of the key differentiators of Plutora's product. Our system can model the organization and give an IT department a way to measure the performance of groups under the management of a particular Director.   This allows you to communicate success or failure as it relates to environments, releases, and deployments, and it gives you the opportunity to identify, which Directors are fully-engaged in addressed release and environment issues versus those who are not.  Stakeholder engagement is critical when making sure that developers don't just throw software over a wall and expect it to be managed without involvement, and Plutora gives directors the right idea when it can roll up issues of problems for a specific release.
  2. Measure Release Management financials. I've found it surprising in my own work across every industry, but companies are very rarely keeping track of the financial impact of a release.  How long does it take?  How many people are involved? And, even a simple question such as, "What is the financial impact of a 50 person incident call related to a release?"  Plutora gives you the ability to generate a report so you can understand just how much effort and how many resources go into a software release.
  3. Use Plutora's Environment Management module. Clearly, we're biased, but I've also haven't seen anything in the market that comes close to the feature we offer for environment management, and I know from what I've seen that environment management is the biggest problem many of our customers face.  Now that companies can spin up 12-20 environments per application at the same time IT departments are being asked to manage more and more projects in massive IT portfolios. I'm talking to environment managers who are in charge of hundreds of environments.  Instead of managing these by change with a manual spreadsheet use Plutora to get a handle on the effort so that you can plan and mature your environment management function from a regressive to an optimizing level of maturity.
  4. Implement Deployment Planning and Master Plan.  Releases always tend to just "come together" at the last minute and software is unpredictable, but budgets demand more predictability.  If you mature your process by creating a deployment plan you'll understand just how important it is to mature your process and move away from a reliance on heroic individuals to make the difference.
  5. Perform Stakeholder Target Reporting for Release Management Clients.   We refer back to the previous item, in an IT department the release and environment management function support the work of Directors.  If directors can be given the information they need and indirectly the business they support can be given targeted reports it will make it easier for the organization to engage with release and environment management.

To learn more about how Plutora has been designed to help move organizations further toward "Optimizing" on the CMM.  Contact us today.

More Stories By Plutora Blog

Plutora provides Enterprise Release and Test Environment Management SaaS solutions aligning process, technology, and information to solve release orchestration challenges for the enterprise.

Plutora’s SaaS solution enables organizations to model release management and test environment management activities as a bridge between agile project teams and an enterprise’s ITSM initiatives. Using Plutora, you can orchestrate parallel releases from several independent DevOps groups all while giving your executives as well as change management specialists insight into overall risk.

Supporting the largest releases for the largest organizations throughout North America, EMEA, and Asia Pacific, Plutora provides proof that large companies can adopt DevOps while managing the risks that come with wider adoption of self-service and agile software development in the enterprise. Aligning process, technology, and information to solve increasingly complex release orchestration challenges, this Gartner “Cool Vendor in IT DevOps” upgrades the enterprise release management from spreadsheets, meetings, and email to an integrated dashboard giving release managers insight and control over large software releases.

@DevOpsSummit Stories
The current environment of Continuous Disruption requires companies to transform how they work and how they engineer their products. Transformations are notoriously hard to execute, yet many companies have succeeded. What can we learn from them? Can we produce a blueprint for a transformation? This presentation will cover several distinct approaches that companies take to achieve transformation. Each approach utilizes different levers and comes with its own advantages, tradeoffs, costs, risks, and outcomes.
Contino is a global technical consultancy that helps highly-regulated enterprises transform faster, modernizing their way of working through DevOps and cloud computing. They focus on building capability and assisting our clients to in-source strategic technology capability so they get to market quickly and build their own innovation engine.
DevOpsSUMMIT at CloudEXPO will expand the DevOps community, enable a wide sharing of knowledge, and educate delegates and technology providers alike. Recent research has shown that DevOps dramatically reduces development time, the amount of enterprise IT professionals put out fires, and support time generally. Time spent on infrastructure development is significantly increased, and DevOps practitioners report more software releases and higher quality. Sponsors of DevOpsSUMMIT at CloudEXPO will benefit from unmatched branding, profile building and lead generation opportunities.
You want to start your DevOps journey but where do you begin? Do you say DevOps loudly 5 times while looking in the mirror and it suddenly appears? Do you hire someone? Do you upskill your existing team? Here are some tips to help support your DevOps transformation. Conor Delanbanque has been involved with building & scaling teams in the DevOps space globally. He is the Head of DevOps Practice at MThree Consulting, a global technology consultancy. Conor founded the Future of DevOps Thought Leaders Debate. He regularly supports and sponsors Meetup groups such as DevOpsNYC and DockerNYC.
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the benefits of the cloud without losing performance as containers become the new paradigm.