Hey IT gurus and tech enthusiasts!
Ever wondered how the pros manage to roll out changes without causing digital pandemonium? Today, we’re diving deep into the world of Release and Deployment Management using the wisdom of ISO 20000. Buckle up!
1. What’s Release and Deployment Management?
This is our shining knight responsible for ensuring changes (often coming from Change Requests or RDMs) go live without hiccups. Whether it’s a solo change or a bunch of them grouped into a single version, this process has it all under control.
2. Laying Down the Groundwork: The Must-Haves
ISO 20000:2018 is pretty clear about what’s needed for effective Release and Deployment Management:
- Release Types: Not all releases are created equal. The organization needs to outline different release types.
- Deployment Planning: Before pushing new or altered services/components live, there’s gotta be a plan. Just winging it? Nope, not here.
- Acceptance Criteria Checks: Before deployment, every release must be checked against documented acceptance criteria. Think of it as the “final exam” for your changes.
- No Go? Make a Decision: If a release doesn’t meet the criteria, it’s decision-making time. The organization and stakeholders get to decide the next steps.
- Baseline Before Deployment: Before setting a release live, capture a baseline of affected configuration items. This ensures you’ve got a record to fall back on.
- Active Environment Deployment: After all checks, the release goes live, ensuring the service’s integrity remains uncompromised.
- Monitoring Success or Failure: It’s not “deploy and forget”. Monitoring how the release fares is critical.
- Keep Everyone In The Loop: Information about release outcomes and upcoming release dates should be made available to other service management activities when appropriate.
3. Why This Matters:
Release and Deployment Management is not just about launching changes. It’s a rigorous process ensuring that every implementation enhances the user experience without causing disruption.
Conclusion:
There’s a method to the madness, and ISO 20000 offers a structured approach to it. As IT service managers, using this standardized approach ensures consistent, high-quality rollouts. Got thoughts or insights about Release and Deployment Management under ISO 20000? Hit us up in the comments!
English 
