Release Management Best Practices

Overview

Issue Management is the practice of capturing and addressing Issues. It is the Release Owner’s responsibility to ensure Issues are captured, triaged, and routed appropriately: some are administrative/operational problems resolved immediately within the current operating Environment, requiring no Change Set or new Release at all; others require a code/configuration change and are added to the Product’s backlog, prioritized, and addressed in a future Release — becoming the substance of a new Feature Release or Patch.

Every Issue, regardless of Type, should be captured against the specific Release ID it was found in/against, the specific Asset/Product/Service it belongs to, and the specific Environment where it was observed.

Issue Type	Description
Incidents/Disruptions	An unplanned interruption or degradation of normal operation of an Asset in a given Environment, discovered after a Release has been deployed.
Bugs/Defects	A confirmed flaw in the behavior of a Release once deployed. Typically flows into the backlog and maps to a future Patch.
Questions/Inquiries	A stakeholder request for clarification or information. Typically resolved immediately, no Change Set or new Release required.
Administrative/Operational Problems	A configuration, access, data, or operational issue resolved directly within the current Environment. No Change Set or new Release required.
Concerns	A stakeholder-raised observation or worry not yet a confirmed Bug/Defect or Incident, but warranting tracking and possible investigation.
Enhancement Requests	A request for new or improved capability. Maps naturally to a future Feature Release.

## Best Practice

Treat every Issue that requires a Change Set as a candidate input to the Product/Service backlog and, ultimately, a future Release — with the Release Owner accountable for triage and prioritization.

Benefit(s)

• Keeps the Roadmap grounded in real operational feedback, not just forward-looking aspiration.