Use cases · Changes, releases and projects

Change the information system without nasty surprises.

From the project to the release, each change is assessed, approved, scheduled and then followed, with its items, teams and deadlines linked.

Benefits

Impacts known before actingThe items affected, and those that depend on them, are worked out from the CMDB; scheduling conflicts and freeze periods are flagged.
Releases followed instance by instanceEach instance has its own status and date; a failure can be escalated to a major incident in one click.
Projects tied to what changesA project milestone is reached on its own when the change is closed or the release is published.

The project sets its phases, tasks and milestones; each planned evolution becomes a change.

The board decides from the record or in session, depending on the change type; each decision is traced.

Approved changes are grouped into a release, deployed instance by instance.

A heightened-monitoring period attaches tickets to the release; the post-implementation review keeps the lessons learned.

Change management Assessment, approval and calendar of changes.
Release management Grouping changes and tracking deployment instance by instance.
Major incidents Crisis coordination when an incident or a deployment calls for it.
Project management Phases, tasks, milestones and portfolio.

The essentials of this page in PDF, to keep or pass on.