Sunday, January 12, 2014

Introducing the Change Calendar

Service offeringAt the end of last year's CAB meeting, we promised that we would start to work on a graphical overview of the planned changes. Today we are making good on that promise with the release of the Change Calendar.

To ensure that the information which the Change Calendar provides is relevant, it only shows work that affects a service. Technically this means that it filters out all tasks, except the ones that are linked to one or more service instances. This is really helpful when, for example, an application change consists of a lot of tasks for risk and impact analysis, approval gathering and development activities. None of these preparations will show up in the Change Calendar. Instead, only the task that transfers the new version of the application to production gets displayed.

Change Calendar
The time bars show how long the execution of a task is expected to take. This bar is blue when the task has not yet been completed; it is gray when the task is already completed. The vertical blue line indicates the current time. The plus and minus buttons in the upper right-hand corner can be used to zoom in or out.

Change Calendar pop-upAs soon as you move your mouse over a task, a pop-up will appear that displays more information.

You can limit what you see in the Change Calendar to only tasks of changes that you manage. You do this by switching from "All Changes" to "Changes Managed by Me" in the upper left-hand corner.

You can also limit the tasks that show up to those that belong to changes which are linked to one or more specific services.

Change Calendar services filterThe Change Calendar can be found in the Analytics console. It can also be launched from the Actions menu when you are working on a change or a task.

This graphical overview should make it much easier for people to review to change implementation activities that are coming up in the near future. The recently completed tasks can also make it easier to identify the cause of new incidents.

0 comments:

Post a Comment