Task: Deliver Release Communications |  |
After a product release has been declared a success and is available for use, all relevant stakeholders should receive a communique stating that fact.
Disciplines: Deployment
Purpose
The purpose of this task is to ensure that the widest possible distribution of accurate information regarding a particular release takes place.
Relationships
Roles | Primary Performer: Deployment Engineer | Additional Performers: Developer
Inputs | Mandatory: Release Communications | Optional: Release
Main Description
This task represents the distribution of communiques that were prepared beforehand as part of the release communications artifact. Although the development team is responsible for preparing the communications, the responsibility for sending the communiques normally is assigned to the deployment engineer, if that is the organizational protocol.
Steps
Validate the communiques
Ensure that the communiques designated for this release are correct, complete, and reflect all the stakeholder groups that must be informed.
Send release communications
Using a pre-planned script, send the communiques in the manner designated in the Artifact: Release Communications. Most of the time, the preferred communication mechanism will be by email, but other methods could include beeper notification, telephone calls, a posting to an internal release website, live or pre-recorded presentations by senior management, etc.
Validate communications were received
If the communiques were sent by email, it may be prudent to request a receipt of delivery to ensure that the notices were received by the intended audience.
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. EPF Copyright.