release

Articles

Release Management Definition What Is Release Management, and Why Is It Needed?

This article talks about what release management is, then tells you how to implement the concepts in an organization by explaining what skills are needed, how release managers work within a team, and how the process is related to continuous integration.

Salman Khwaja's picture Salman Khwaja
Harmony in Releases Achieving Enterprise Release Harmony

An enterprise release consists of individual releases, some independent and some dependent. If we think of an enterprise release as a song, then the individual releases can be thought of as the musical notes that make up the song. This article discusses problems associated with an enterprise release and ways in which these problems can be overcome, resulting in release harmony.

Pradeep Prabhu's picture Pradeep Prabhu
Testing Requirements Redistributed Testing: A Shift to Refine Requirements

In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?

Paul Gerrard's picture Paul Gerrard
Release Management and Deployments: Why Is This So Important?

Why do we wait to discuss releases and deployments until the last minute? Is this a result of our lack of planning and knowledge, or is there a deeper reason why we fail to plan properly? Joe Townsend digs into the release and deployment portions of the SDLC to try to shed some light on why we tend to neglect these crucial steps.

Joe Townsend's picture Joe Townsend
Release Management and Deployment Essentials

Business requirements often dictate how changes in release management are addressed. But by following some essential practices and core beliefs, database deployment does not have to result in the headaches once caused.

Uri  Margalit's picture Uri Margalit
photo whiteboard showing theme we needed to finish; right side is the new theme We're Agile

I always recommend to teams newly transitioning to agile that they keep every iteration the same length. This helps them learn to manage their time, and after a few iterations they'll start to get a rhythm. Hopefully, they'll learn to work incrementally, doing testing and coding concurrently as part of one development effort, so that user stories are finished throughout the iteration, and testing isn't pushed to the last day.

Lisa Crispin's picture Lisa Crispin
Wrangling a Release: The Role of Release Manager

Companies that develop multiple products often struggle with how to ensure they all work together as a solution and struggle with how to get the deliverables from various products together into a working release. Project managers and product managers have other priorities to handle. So who handles a release that wrangles together multiple project deliverables from multiple products that define a solution or complex release? The answer is the Release Manager.

Mario  Moreira's picture Mario Moreira
CM as Communication and Coordination Enabler

This article includes some of the material that Geoff Thorpe presented at a BCS CMSG event where he discussed the control of applications using change management, release management,
and configuration management techniques. He discusses applications control from a hardware and software perspective.

A Framework for Agile

Bob Aiello discusses how CM and agile practices can go hand in hand - provided that you have a solid framework to work with. With agile's popularity seemingly always on the rise, alongside the need for CM, learn how having both benefits everyone onboard.

Bob Aiello's picture Bob Aiello
An Agile Approach to Release Management

For teams practicing Agile Software development, value working software over other artifacts, a feature from the release plan is not complete until you can demonstrate it to your customer, ideally in a shippable state. Agile teams strive to have a working system ("potentially shippable") ready at the end of each iteration. Release Management should be easy for an ideal agile team, as agile teams, in theory, are ready to release at regular intervals, and the release management aspect is the customer saying, "Ship it!."

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.