What should a release policy include?

Question

Options

• ARoles and responsibilities across all the service transition processes
• BRoles and responsibilities for updating the configuration management database (CMDB)
• CCriteria and authorization to exit early life support and handover to the service operation function
• DHow request for changes (RFCs) are approved for software releases in the IT production

• A
  2% (1)
• B
  2% (1)
• C
  91% (51)
• D
  5% (3)

Explanation

According to ITIL, a release policy defines the rules and expectations that govern how releases are managed throughout their lifecycle. A key element of this policy is defining the criteria and required authorization needed to formally exit the Early Life Support (ELS) period - the stabilization phase immediately after a release goes live - and officially hand operational responsibility over to the service operation function (e.g., the service desk and operations teams). Without clear exit criteria, services may be handed over prematurely or held in ELS indefinitely. Option A is too broad and covers all service transition processes. Option B relates to configuration management procedures. Option D is part of change management policy, not release policy specifically.

No community discussion yet for this question.