Documentation forSolarWinds Service Desk

Change Calendar

If you chose to click to this page, we understand you want to make the most of your Change Calendar.

Change calendars can drastically improve your change processes – allowing your team to be more successful by causing fewer impacts to the services you offer your employees. Below are a number of factors to consider when implementing scheduling changes.

Scheduling

Properly scheduling changes ensures you are aware of upcoming and/or overlapping changes prior to deployment. Many CAB meetings focus on validating the correct build for change and making sure it is scheduled at a time that has the least impact on daily productivity. A visual representation can be very beneficial.

Let's delve into:

  • Avoid Change Collisions: Your organization may have several changes on the calendar at any given time. It is important to take a holistic approach, as one change could greatly impact the success of another. The change calendar ensures you can properly visualize all the upcoming changes to ensure they are scheduled to support the business.
  • Aligning with other calendars: Another major benefit with pushing your changes to your own calendar is that it allows you to overlay your change calendar with other calendars to promote better scheduling. Some examples are:
    • Some organizations have “black-out” dates, dates where the business does not allow any change implementation to avoid disruptions. You can align this with your change calendar to avoid scheduling during those dates.
    • Your “PTO” calendar can be maintained to where others can view who will be out of the office during a given period of time. Align this with your change calendar to ensure you have the proper people available who will be implementing the change and adequate support staff.

    • At times there are other departmental projects that are not considered a change but still could impact scheduling. If you have project milestones or tasks on a calendar, you can align your changes to ensure successful deployment and minimal effect to employees.

  • Consolidate Changes: Find opportunities to optimize your release cycles. Two examples are described below:
    • You may have two upcoming changes that impact the same server. Each individual change will take the server offline for 2 hours, however, you may be able to combine the changes and only take the server offline for a total of 3 hours. This will effectively reduce downtime through more efficient change management.
    • A patch is required on a test Windows VM. Your infrastructure team would like to set the install to Friday night and monitor it over the weekend. This will bring the test machine down on Friday night. In addition a product team is updating the test region of an app running on that same machine on Saturday. If they sit in different offices, they would have no way to know they should collaborate on the upcoming Changes.