Milestones

In Neurons for ITSM, release management uses milestones to plan and increment the release process. By default, milestones are created for major releases; however, you have the option to manually create milestones for emergency and minor releases. See Working with Milestones for best practices when using milestones.

•By default, approval workflows are defined for release milestones that are generated using the template for major releases.

•Along with the Release Review Board, stakeholders are also identified for the release.

•A request for release might come from Change Enablement. When the change is linked to the release, the schedule dates for the change are driven by the release schedule and become read-only. The Release Manager also creates release packages to roll out configuration items included as part of a change.

•Release Managers can also view the cost of the release while it is worked on, and get a final cost associated with the release upon the closure of the release or a milestone upon the closure of the milestone.

•Release Managers can also monitor and track the metrics associated with releases by reviewing the release reports.