You are on page 1of 10

WHITE PAPER

The Role of Release


Management in a DevOps World
Release management is more important than
ever in the fast-paced, distributed DevOps world.
Executive Sumary

When talking about DevOps, it’s easy to focus too application or infrastructure. Release management
much on the speed of each individual step in the tools make it easier for businesses to manage
software creation and deployment process while the technical and organization complexity of
losing sight of the both the business objectives and distributed software architectures, distributed teams
how well everything is working together. Release and distributed responsibility for application health.
management takes a more holistic view, looking This makes it possible to accurately
both at software in the context of its business evaluate risk, see complex dependencies and,
goals as well as how each piece of the technology ultimately, connect across teams in the IT
stacks works together both in production and department as well as other business stakeholders.
during the development process. A key focus of Release management isn’t just about creating better
release management is zooming out far enough software, it’s about ensuring business alignment,
to understand complex dependencies and thus reducing risk, and improving the speed of software
minimizing risk associated with any change to the delivery for the business.
pharmaceutical company. On the one extreme,
What Is Release Management? Friend and Foe
there are people who still think of release
management as creating a build and
The role of release management has changed as “You are an enabler to get something out,
doing a deploy.
organizations move to a more DevOps-focused but you’re also the gate to say something
process, but there has never been a ‘standard’ is not going to get out,” explains the
Then there are others who think of release
definition for release management. In the ‘old Director of Release Management of a global
management and project management as the
days,’ release management referred to shipping pharmaceutical company, about the role of
same, or release management is something project
a finished piece of software into production. The release management teams. “You could be a
managers handle. This is a more mature view but
most expansive definitions of release management friend or you could be a foe to the same team
still falls short of what true release management is.
in a waterfall-style development environment five hours later.”
involved ensuring that a piece of software
True release management is everything you
met security and governance requirements before The goal of release management is successful
need to do to plan, coordinate, establish resources,
becoming publicly available. The least expansive deployment. The more visibility you have
develop, test and facilitate the transition into
definitions referred just to the technical steps into the entire system, the less likely you’ll
production for a piece of software. Its role is
required to take a piece of code from need to put the brakes on further down the
to coordinate the relationship between project
the pre-production environment to the pipeline, because you’ll be able to identify and
management, testing and quality assurance,
production environment. fix potential problems much sooner in the
configuration management and deployment to
development process. Using integrated release
ensure that every release follows compliance and
Release management is evolving as companies management tools gives release management
security best practices and company guidelines.
adopt a DevOps-style approach… but not everyone teams the real-time information needed to
Release management ensures that all the
is one the same page about the role of release spend more time being friends and less time
stakeholders are working together and understand
management. “In the IT field, there actually could slamming on the brakes at the last minute.
how components built by different teams will work
be quite a few interpretations that are widely
together in the production environment.
varied on what release management is,” explains
the Director of Release Management at a global
Solving the Whole Puzzle Release management is a way to zoom out and ‘Don’t worry about me, I’m just going to spray
see the entire picture. This includes the end-to-end stuff out there and see what happens,” explains
process of idea to software development to value the Director of Release Management at a global
A mature release management system looks at the
delivered to customers as well as the complete pharmaceutical company. “The reality is you need
entirety of the software development process, from
view of company’s technical environment, from Swiss-clock precision.”
identifying a business need and determining how to
where everything is in the application lifecycle
meet that need with software to developing, testing
to the complete tech stack down to the servers. Release management provides the guardrails to
and deploying that software to end customers.
Release management is about understanding the make Swiss-clock precision consistent across an
“Release management is the end, think of it as the
big picture—how a group of applications moves entire enterprise. Here’s how it fits into the
end to end process of getting an idea to production,
through its lifecycle, how each application interacts DevOps world.
all the things that need to happen as part of that,”
with and depends on other parts of the tech
Dalibor Siroky, CEO of Plutora, explains. “And that
stack, where security vulnerabilities exist and the The Release Management Ecosystem
would include, how does that ideation phase feed
risk any particular deployment has of blowing up
into the next phase, how does the design phase
the whole system. Release management involves zooming out, to
build into the construction phase, so those iterative
phases ... and what are the handoffs, how do understand how your organization is using software
In a DevOps world that’s focused on moving fast, to meet customers’ needs.
people collaborate?”
getting this complete picture is the only way to
both make sure software is meeting its intended Release management refers to managing the
“How does that ideation phase
business goals and being delivered in a way that entire process, from business logic to customer
feed into the next phase, how does
doesn’t go wrong regularly. “Fundamentally, delivery, for a single application.
the design phase build into the the business is saying ‘how can I get this idea to
construction phase, so those iterative production faster, so that I can get generate more Enterprise release management refers to
phases ... and what are the handoffs, benefits for my customer?’” explains Siroky. managing the entire portfolio of an organization’s
how do people collaborate?” applications, from business logic to value delivered
“The notion of working DevOps style and delivering to customer, including understanding how these
— Dalibor Siroky, Plutora CEO fast, to many people, is sort of the equivalent of application interact with and depend on each other.
Value stream management is the broadest to organize cross-team and cross-departmental
Why DevOps Needs Release
term, that zooms out to get the widest view of collaboration, everything from information sharing
Management
how software is contributing to business value. to collaboration is done in an ad-hoc, informal,
Value stream management involves creating a fragmented way.
Release management is crucial to successfully
feedback loop to evaluate how well the finished
managing the complexity that the combination
software product is meeting the business need as
of DevOps and distributed, microservice-based “The amount of moving parts and
originally identified—and iterating based on how
architectures have introduced into the application dependencies is incredible, and
customers interact with the software. Value stream
landscape. In the real world, organizations that unless everybody’s on the same
management ties IT in with business metrics
are following DevOps practices without integrating page and you have a flight screen,
and other departments, depending on the
release management often run into the a radar view of the entire sky, it’s
software’s goal.
following challenges.
a statistically likely that things will
break, probably fairly often,”
Fragmented information, Informal
Collaboration — Director of Release Management at global
pharmaceutical company
DevOps prioritizes the creation of small teams
and giving them wide latitude to create and
deploy applications. This process helps speed up “The vast majority of the project programs focused
the application development and deployment around business capabilities have dependencies
process, but creates and perpetuates the myth in and out, upstream downstream, but a good
of entirely self-sufficient teams. In reality, both portion of them think they live in their world,”
the teams and the software they are creating has explains the Director of Release Management at a
complex dependencies. The DevOps process tends global pharmaceutical company. Often, individual
to create information silos, making it each team teams are too low-level and focused on specific
a black box. In the absence of a formal system functionality—authentication management, for
example—to be able to see the bigger picture or different responsibilities in the application lifecycle. but in an environment where information is often
even how authentication management fits into and In addition, each team might follow a different siloed, dependencies are poorly understood, teams
depends on other parts of the application. DevOps development and deployment procedure, are delivering as fast as possible and everything is
gives the illusion of independence—and use different tools and write applications in a in constant flux, the decentralized responsibility for
when one team changes or deletes a resource different language. releases is a recipe for disaster.
another team’s app depended on, the
consequences can be dramatic. Constant change means that information has to be “Now we’re dealing with more pipes, from more
available in real-time, because it can be out-of-date practitioners who practice many different ways,”
In addition, it’s difficult for anybody to get a immediately. But relying on the informal, point-to- explains the Director of Release Management.
complete view of an organization’s suite of point information gathering common in the real “The quality of planning, integration, coordination
applications. “Information is often fragmented, world makes it impossible to get an accurate view is all over the map. So bringing it all together to
informal and not capable of delivering true of the changing application landscape. something cohesive, that in the end not just works
decision-making information to key stakeholders,” together, but is properly timed and doesn’t blow
Siroky explains. Businesses create software to meet Decentralized Accountability anything else up. That is a challenge.”
business objectives, but the lack of visibility into the
organization’s software pipeline makes it difficult to In the past, there was more of a centralized Misunderstood Risk
make informed business decisions. gatekeeper that all new code had to go through.
DevOps breaks down this centralized role, creating Constant change, decentralized responsibilities
Constant Change more acceptable pathways to get into production. and lack of information make it hard for anybody
Cross-functional, product-oriented teams that to truly understand the risk associated with any
“Everything is shifting all the time,” explains the include experts in development, testing, security individual deployment, which requires granular
Director of Release Management. “People change, and deployment have the autonomy to deliver visibility into an applications entire stack, starting
the roles change, there’s a lot of shifts in and out of their code directly—as well as the responsibility with the server operating system as well as all the
responsibility.” This state of constant flux makes it to run the application once it deploys. There’s no upstream and downstream dependencies.
difficult to get everyone in an organization on the centralized oversight at any part of the application
same page. Everyone has different cycle times and lifecycle. This is autonomy is a key part of DevOps,
The inability to understand risk profiles goes to the
Integrating Automated, Holistic
core of what happens when you have distributed
Release Management with DevOps
team, diverse working methods and incomplete
information sharing—in other words, DevOps
When release management is integrated
without release management. “The amount of
moving parts and dependencies is incredible, and into the automated pipelines and
unless everybody’s on the same page and you have processes that are at the core of the
a flight screen, a radar view of the entire sky, it’s a DevOps development paradigm,
statistically likely that things will break, probably there’s a way for information to be
fairly often,” explains the Director of Release shared between engineering teams
Management at a global pharmaceutical company. as well as with other business-level
“The question is what breaks? Is it something you
stakeholders. Creating a formal,
could live with, or is it a real issue?”
automated information repository, as
well as standardizing the release steps
and making it easy to visualize complex
dependencies, brings the DevOps chaos
back under control. Here’s how an
integrated release management helps
organizations tackle the challenges
DevOps creates without infringing on
the speed and autonomy that makes
DevOps successful.
Risk Transparency Without release management tools, release yours, are in their workflow. This makes it possible
managers are asked to evaluate risk by looking at for teams to see how changes to the application
past releases and using past experience to predict affect others, and vice versa, at every step of the
Comprehensive release management tools provide
future performance—a process that inevitably process. This advance notice of possible issues
transparency into the entire toolchain as well as
involves gut feelings. Using a tool like Plutora takes down the line makes it possible to coordinate and
the web of upstream and downstream
the guesswork out of this process by looking at prevent potential collisions from cause
dependencies, making it possible to accurately
the complexity and dependencies of the release production outages.
evaluate different kinds of risk factors, from
to make accurate risk assessments as well as
whether or not the deployment will introduce a
recommend ways to reduce that risk. “In a desire to increase frequency,
security risk to how likely it is to break another
team’s application. Understanding what the you typically get a high degree of
possible consequences of a failed deployment are Make Coordination a Reality automation, you get a higher degree
can both inform whether or not a deployment is of collaboration and you can’t do it
ready for production as well as what needs to be DevOps might be about breaking down the without information sharing. That
monitored post-deployment. barriers between development and operations,
information sharing comes from more
but it can create barriers between individual
of a decentralized structure, and that
A major part of the risk transparency is the ability teams as well as between engineering teams and
decentralized structure needs to
to understand dependencies before one causes an other stakeholders, like security, compliance or
support and supply the information
outage—ideally, in fact, before an application legal departments. Integrated, automated release
is even at the testing phase. Comprehensive management tools surface information seamlessly, seamlessly”
release management surfaces dependency in real time, without a need to interrupt developers’
workflow. — Dalibor Siroky, Plutora CEO
information automatically before developers
alter or create an application, providing better
information for that practitioner to keep in mind Information sharing makes it possible not only to
from the very beginning. know that your application’s dependencies, but also
to see how where other teams, whose applications
have upsteam or downstream dependencies on
See the Big Picture what’s the idea that we’re building, why are we now testing is the product-oriented team’s
building it?” explains Siroky. “The other part is, is it responsibility. Release management is currently
delivering value to the customer?” handled almost exclusively by dedicated release
Value stream management tools provide a catwalk
management teams, outside of the product-
over the factory floor, giving business stakeholders
If you don’t have a view of the end-to-end process, oriented development and operations team. But as
as well as engineering leaders a view of the entire
you can only optimize individual pieces of the DevOps adoption becomes more mature, release
software ecosystem that includes everything from
pipeline rather than the entire process as a whole. management responsibilities will be transferred
idea to production. It’s easier to see bottlenecks in
When you lay it out and look at how everything to one of the product-oriented team’s members
the process or places where current procedures
connects to each other, you can start to optimize the or the team as a whole, though possibility still with
aren’t working as well as they should In addition,
entire process, from business logic through customer coaching from a release management group.
this zoomed-out view includes not just information
feedback. This makes it possible to iterate based on
about how the software is performing from a
how well a piece of software is meeting customer While responsibility for release management will
technical perspective, but also how it
needs and delivering its intended business value. become more distributed, the need for centralized
contributes to business goals.
control will never disappear—especially in
Release Management in Product- industries that have strict compliance requirements.
Optimize for Customer Value
Oriented Teams Automating as much of the release management
process allows a centralized release manager to
Release management is about more than creating
A key part of the DevOps transition has been create the guardrails that teams throughout the
better software and reducing outages. Ultimately,
moving to self-contained, product-oriented company will have to respect. Building release
comprehensive release management tools allow
teams that can handle an increasingly large management into the development process at all
organizations to worry less about the technical
share of the application lifecycle, including stages, inside of pre-defined guardrails and policies,
nitty-gritty and more about how they use software
designing, building and running the application. gives product-oriented teams the agility they need
to create value for customers and value for the
As companies move to more mature DevOps to move fast while ensuring that compliance,
business, leading to better customer experiences
models, they incorporate more roles into the security and release management best practices
and higher net promoter scores. “The starting point
DevOps team. At one point, testing was handled are followed consistently.
of a release is at the planning and scoping phase,
by testers external to the development team—
Conclusion

Most organizations adopt DevOps in an effort to without an unacceptable level of risk that any
move faster and provide value to internal and given deployment will blow up the entire system in
external customers more quickly. Particularly at an unpredictable, hard-to-debug ways.
enterprise scale, however, DevOps adds complexity
from a technical and human resources perspective. True release management gives companies a zoom-
Integrating comprehensive release management out view of the application lifecycle that makes it
increases the visibility into the application lifecycle possible to identify inefficiencies and stitch together
and creates guardrails to ensure everyone is the creative parts of application design with the
following best practices. Surfacing information tasks best handled by automation. Zooming
about dependencies between teams, getting a out also puts the application in the context of
complete view of the risk profile and enforcing the business and the business goals, allowing
security and compliance best practices company- organizations to optimize not just for software
wide makes it possible to move at the speed quality, but for value delivered to customers.
companies expect from DevOps

About Plutora
Plutora, the market leader of value stream management solutions for enterprise IT, improves the speed and quality
of software creation by capturing, visualizing and analyzing critical indicators of every aspect of the delivery process.
Plutora orchestrates release pipelines across a diverse ecosystem of development methodologies, manages hybrid
test environments, correlates data from existing toolchains, and incorporates test metrics gathered at every step.
The Plutora Platform ensures organizational alignment of software development with business strategy and provides
visibility, analytics and a system of insights into the entire value stream, guiding continuous improvement through
Learn more: www.plutora.com
the measured outcomes of each effort.
Email: contact@plutora.com

You might also like