Back to Assessments & Documents
IT Service Management Active

Service Transition, Release and Deployment Maturity Assessment

A 47-question diagnostic across 8 domains that evaluates how new, changed and retired services are designed, planned, released, accepted, deployed and handed over to operations, including AI models, prompts and agents. W...

Start Assessment

Overview

A 47-question diagnostic across 8 domains that evaluates how new, changed and retired services are designed, planned, released, accepted, deployed and handed over to operations, including AI models, prompts and agents. Written for the head of service transition or release management who needs to answer: do our releases reach users ready to be run and supported, and do we know when they are not?

Detailed Description

Releases often pass every test and still fail in operation: monitoring is missing, the service desk hears about the release from users, the runbook was never tried, a data migration is short by a few thousand records, or a supplier update lands in the middle of month-end. Early life support ends on a date rather than on results, and nobody owns the service afterwards.

This assessment follows the order in which a dependable transition is run: a transition policy, roles and models scaled to risk, with releases authorized through change management; a design record with availability, capacity and service level requirements and acceptance criteria set at design, a transition plan, rehearsed cutover and business readiness; release policy, scope freeze, packaging of signed components from authorized sources, release notes, emergency and supplier releases; validation against acceptance criteria, operational acceptance tests, knowledge transfer, support readiness, accepted exceptions and a recorded go/no-go; deployment windows, deployment approach by risk, phased distribution, verification, rollback decisions and feature flag releases; early life support, exit and handover, closure review, lessons and service retirement; AI models, prompts and agents released as releases; and measurement and improvement.

It tests the transition decision and the hand-off to each neighboring model through named Input documents: Change Management, Technology Service Catalog, Service Level Agreements and Performance, Service Availability Management, Capacity Performance Management, SRE, DevOps and ITSM Convergence, DevOps Engineering, Configuration Management, Knowledge Management, Service Desk, Problem and Root Cause Management, Incident Management, Service Integration and Management (SIAM), AI Pipeline and MLOps, AI Use Case Lifecycle Management and Continual Service Improvement. Each question is scored on whether the practice is Documented, Implemented and Effective.

Assessment Details

Audience

Head of service transition, release manager, head of IT operations. Secondary: service owners, operations acceptance and support leads, service desk managers, product and platform engineering leads, change managers and ML platform leads.

Purpose

Shows where releases reach production without operational readiness, where acceptance is decided on opinion rather than evidence, where deployments run outside agreed windows or without a rollback decision, where support learns about changes from users, and where AI changes bypass release control. Gives each gap a concrete next step and a measurable target.

Effort

Initial assessment: 4 to 6 hours of facilitated sessions with service transition, release management, delivery and platform engineering, operations and support, and service owners. Evidence gathering: transition and release policies, design records, transition plans, release records, readiness checklists and go/no-go records, deployment logs, early life support plans, closure reports and release measures.

Cadence

Every six months, and after a failed major release, a major platform or provider transition, or a significant change in how AI systems are released.

Framework Alignment

ISO/IEC 20000-1:2018 ITIL 4 COBIT 2019 ISO/IEC 27001:2022 SLSA v1.2 Google SRE Workbook DORA Capabilities ISO/IEC 42001:2023 NIST AI RMF 1.0 NIST AI 600-1 OWASP Top 10 for Agentic Applications 2026

KPIs

  • Releases Live with Unmet Criteria - Number of releases that went live with a readiness criterion unmet and not covered by an accepted exception. Threshold: 0.
  • Readiness Met at Go-Live - Share of releases that went live with all readiness criteria met and no exceptions. Target: 90% or higher (model target).
  • Exits with Criteria Unmet - Number of major releases and new services in the quarter that exited early life support with one or more exit criteria unmet. Target: 1 or fewer per quarter (expert judgment).
  • Releases with Readiness-Gap Incidents - Share of major releases with a high-priority incident in the first 30 days traced to a readiness gap. Target: 5% or fewer (model target).
  • Change Failure Rate - Share of production deployments that caused a failure needing remediation. Target: 15% or fewer, set by expert judgment informed by the DORA reports (high performance band about 10% in 2023 and about 20% in 2024), not equal to a DORA band.

Dependencies

Change Management (v8.9.6): change policy scope, risk model, release plan review, calendar, change windows and blackout periods, per-change verification, emergency procedure, back-out plans, post-implementation review, lessons, standard change models and KPI definitions (1.1, 1.3, 1.4, 1.5, 2.5, 3.5, 5.1, 5.4, 5.5, 6.3, 6.4, 7.5, 7.6, 8.1). Technology Service Catalog (v10.9.6): pipeline gate decisions, Service Acceptance Criteria and retirement steps (2.1, 2.3, 4.4, 6.5); Service Level Agreements and Performance (v5.9.6): service level requirements and maintenance windows (2.2, 5.1). Service Availability Management (v6.9.6) and Capacity Performance Management (v6.9.6): availability requirements, capacity requirements by reference, release safety, vendor update rings, failover and load tests (2.2, 3.6, 4.1, 4.2, 5.2). SRE, DevOps and ITSM Convergence (v4.9.6): service record, runbooks, production readiness review, progressive delivery and synthetic monitoring (1.2, 4.2, 4.6, 5.2, 5.4, 5.5, 6.1, 6.2); DevOps Engineering (v1.9.6): test strategy, artifact repository, deployment records, delivery measures including deployment rework rate, flag lifecycle and clean-up, and agent access (3.3, 4.1, 5.6, 5.7, 7.5, 8.2). Configuration Management (v9.9.6): definitive media library and post-deployment updates (3.3, 5.6); Knowledge Management (v10.9.6): runbook validation and AI-drafted content review (4.3, 7.4); Service Desk (v7.9.6): release readiness checklist (4.4). Problem and Root Cause Management (v8.9.6): known errors (4.5); Incident Management (v9.9.6): incidents linked to changes (8.3); Continual Service Improvement (v8.9.6): improvement register (8.5); Service Integration and Management (SIAM) (v6.9.6): provider transitions and exit plans (2.7). AI Pipeline and MLOps (v11.9.6): configuration release, prompt versions, golden sets, quality measures and model rollback (7.1, 7.2, 7.3); AI Use Case Lifecycle Management (v4.9.6): AI System Card (7.2); Agile Project Management (v1.9.6): project handover (2.4); Organizational Change and Adoption Maturity Assessment v3.9.6: people-side readiness (2.6).

Assessment Outline

(8 domains · 47 questions)
  1. 1

    1 Transition Governance and Policy

    Service transition policy and triggers, roles and decision rights, transition models scaled to risk, release authorization through change management and the shared release and transition calendar

    • 1.1 Service Transition Policy 1 questions
    • 1.2 Transition Roles and Decision Rights 1 questions
    • 1.3 Transition Models Scaled to Risk (Bridge) 1 questions
    • 1.4 Release Plan Authorization through Change Management (Bridge) 1 questions
    • 1.5 Release and Transition Calendar (Bridge) 1 questions
  2. 2

    2 Service Design and Transition Planning

    Design record for new or changed services, non-functional and service level requirements, acceptance criteria set at design, the transition plan, cutover and data migration, business and user readiness and transfers between providers

    • 2.1 Service Design Record 1 questions
    • 2.2 Non-Functional and Service Level Requirements (Bridge) 1 questions
    • 2.3 Acceptance Criteria Set at Design (Bridge) 1 questions
    • 2.4 Transition Plan 1 questions
    • 2.5 Cutover and Data Migration 1 questions
    • 2.6 Business and User Readiness 1 questions
    • 2.7 Service Transfer Between Providers (Bridge) 1 questions
  3. 3

    3 Release Planning and Packaging

    Release policy, types and cadence, scope freeze and dependencies, packaging from authorized components, release notes and notices, emergency and hotfix releases, and supplier and SaaS releases

    • 3.1 Release Policy 1 questions
    • 3.2 Release Scope Freeze and Dependencies 1 questions
    • 3.3 Release Packaging from Authorized Components (Bridge) 1 questions
    • 3.4 Release Notes and Notices 1 questions
    • 3.5 Emergency and Hotfix Releases (Bridge) 1 questions
    • 3.6 Supplier and SaaS Releases (Bridge) 1 questions
  4. 4

    4 Service Validation and Operational Acceptance

    Validation of test evidence against acceptance criteria, operational acceptance testing, knowledge transfer to operations, service desk and support readiness, accepted exceptions and known errors, and the go/no-go decision

    • 4.1 Service Validation Against Acceptance Criteria (Bridge) 1 questions
    • 4.2 Operational Acceptance Testing 1 questions
    • 4.3 Knowledge Transfer to Operations (Bridge) 1 questions
    • 4.4 Service Desk and Support Readiness (Bridge) 1 questions
    • 4.5 Accepted Exceptions and Known Errors (Bridge) 1 questions
    • 4.6 Go/No-Go Decision 1 questions
  5. 5

    5 Deployment Governance

    Deployment windows, deployment strategy by risk, phased distribution to sites and devices, post-deployment verification, rollback and fix-forward decisions, deployment and configuration records, and feature flag releases

    • 5.1 Release Scheduling within Change Windows (Bridge) 1 questions
    • 5.2 Deployment Strategy by Risk (Bridge) 1 questions
    • 5.3 Phased Distribution to Sites and Devices 1 questions
    • 5.4 Release Verification against Acceptance Criteria 1 questions
    • 5.5 Release Rollback and Fix-Forward Decision 1 questions
    • 5.6 Deployment and Configuration Records (Bridge) 1 questions
    • 5.7 Feature Flag Releases (Bridge) 1 questions
  6. 6

    6 Early Life Support and Transition Closure

    Early life support, exit and handover to operations, transition closure review, transition lessons and service retirement transitions

    • 6.1 Early Life Support 1 questions
    • 6.2 Early Life Support Exit and Handover 1 questions
    • 6.3 Transition Closure Review (Bridge) 1 questions
    • 6.4 Transition Lessons Learned (Bridge) 1 questions
    • 6.5 Service Retirement Transitions (Bridge) 1 questions
  7. 7

    7 AI and Agentic Releases

    AI models, prompts and agent configurations released as releases, AI release acceptance, watch periods after AI releases, AI-drafted release content, agents that run deployments and AI-assisted readiness analysis

    • 7.1 AI Models, Prompts and Agents as Releases (Bridge) 1 questions
    • 7.2 AI Release Acceptance (Bridge) 1 questions
    • 7.3 Watch Period After AI Releases (Bridge) 1 questions
    • 7.4 AI-Drafted Release Content 1 questions
    • 7.5 Agents That Deploy (Bridge) 1 questions
    • 7.6 AI-Assisted Readiness Analysis 1 questions
  8. 8

    8 Transition Measurement and Improvement

    Release and transition measures, shared delivery stability measures, transition quality from early incidents, stakeholder feedback, and KPIs with improvement actions

    • 8.1 Release and Transition Measures 1 questions
    • 8.2 Delivery Stability Measures (Bridge) 1 questions
    • 8.3 Transition Quality from Early Incidents 1 questions
    • 8.4 Stakeholder Feedback on Transitions 1 questions
    • 8.5 KPIs and Improvement 1 questions

At a Glance

Category IT Service Management
Type Free
Roles 6
Domains 8
Questions 47
Start Assessment

Still have questions? Get in touch

ITSGovernance
  • Twitter

Contact us

ITSGovernance