Release Management

Practical Case

Change Management has approved (see the practical case in the previous chapter) an RFC having as its main objectives:

• Increasing the capacity of the company's web servers in order to enhance connectivity and response capacity.
• Developing a series of WebServices permitting:
• Direct integration of the online ordering system with the company's ERP system.
• Tracking the ordering process from end to end.
• Remotely managing the whole supply chain jointly with suppliers.
• Redesigning the website to enhance usability and optimise it for search engine indexing.

Release Management is in charge of the process of developing, buying, testing and distributing the new versions of hardware and software concerned. For this purpose:

• The new hardware needs are assessed in collaboration with Capacity Management and Availability Management and the hardware is bought and configured.
• They contact their usual web development suppliers to define the specifications of the new software precisely and to draw up a schedule for development.
• The web structure is duplicated, i.e. new servers are bought so that the old ones can continue providing continuous service and are immediately available for a possible back-out.
• Translation scripts are written allowing the new data to be saved on the old version to avoid data being lost in the event of a back-out.
• A schedule is set for testing by real users so they can give their approval to the new service.
• A two-stage deployment is planned:
  1. The whole web structure, excluding the data, is incorporated directly onto the company's ERP.
  2. The process is completed with the integration of web orders using WebServices on the ERP.
• A user manual is written describing the new release and a FAQ page is created on the web that includes the queries users raised most frequently during the testing phase.
• Users are informed about the new release and warned of possible short interruptions to service during installation.
• The new release is installed.
• A master copy of all the software is stored in the DSL.
• The CMDB is updated.