7 proven practices to strengthen release management
DESCRIPTION
The increased amount of deployments performed in a short amount of time raises the possibility of human error, which can result in failed deployments or outages. The following tips will help stabilize and strengthen the release management process. "The ABCs of Continuous Release and Deploy in a DevOps approach" http://www.slideshare.net/Urbancode/final-24549349TRANSCRIPT
7 Proven Practices to Strengthen Release Management
IBM Corporation ©2013
This presentation is brought to you by:
Cleveland, OHIBM UrbanCode Products
IBM Corporation ©2013
You're a Release Manager trying to release applications
to production and keep up with business needs.
IBM Corporation ©2013
Different teams and tools used for each
project create a release nightmare
and potentially extend the release weekend.
IBM Corporation ©2013
The following are 7 steps for effective release
management
IBM Corporation ©2013
1 Establish a single source of truth
IBM Corporation ©2013
When orchestrating a global application release, create a single source of truth that will update in real time.
doing so will coordinate all parties responsible for the release and provide visibility and traceability into who created what, and when.
Why
IBM Corporation ©2013
When orchestrating a global application release, create a single source of truth that will update in real time
Doing so will coordinate all parties responsible for the release and provide visibility and traceability into who created what, and when.
Because
IBM Corporation ©2013
2 Automate painful tasks
IBM Corporation ©2013
Automate as much of the deployment process as you can.
Automation provides a secure and successful way to complete steps crucial to deployment of applications.
Why
IBM Corporation ©2013
Automation provides a secure and successful way to complete steps crucial to deployment of applications.
Because
IBM Corporation ©2013
3Make
“what is where”visible
IBM Corporation ©2013
IBM Corporation ©2013
Because
Not knowing what is on a machine, or an environment is exceptionally risky.
IBM Corporation ©2013
4Make
certifications and approvals visible
IBM Corporation ©2013
Define a quality gate to establish minimum entrance requirements to an environment.
Certifications and approvals ensure quality
Why
IBM Corporation ©2013
Certifications and approvals ensure quality.
Because
IBM Corporation ©2013
5Make the
release plan easy to consume
IBM Corporation ©2013
A release plan that can be edited on the fly, and easily understood, makes it obvious to everyone what the impact of the change is.
A release plan that can be edited on the fly, and easilyWhy
IBM Corporation ©2013
A release plan that is too hard to understand will largely be ignored.
Because
IBM Corporation ©2013
Companies can ease the pain of deploying to production by implementing these release management practices.
IBM Corporation ©2013
Click Here
IBM Corporation ©2013
Visit us on www.IBM.com
IBM Corporation ©2013