Task: Develop Release Communications |  |
Stakeholders should be notified when a product (or feature set) is placed into production.
Disciplines: Deployment
Purpose
The purpose of this task is to create the content and criteria to identify who is notified and to describe how they are notified after a release is deployed successfully to the production environment.
Relationships
Roles | Primary Performer: Deployment Engineer | Additional Performers:
Inputs | Mandatory: Deployment Plan | Optional: Release Controls
Outputs | Release Communications
Main Description
When a release is pushed to production, all the Stakeholders of that product should be notified that the event has happened and what the release means to each of the Stakeholders. Often, the output of this task does not need to be created from scratch; for products that plan multiple releases, just updating the communique details for each release might be enough. However, if any of the Stakeholder groups change, or there is a significant difference in the product distribution, more significant content might need to be developed. In any case, communicating effectively to the End User community is important. A Development Team can develop high quality software, but if messaging to the Stakeholders is conducted poorly or not at all, the End User experience might be degraded. By simply answering the questions "who, what, when, where, why, and how" in a format appropriate for each Stakeholder group, a product release can become a more satisfying experience for all those involved.
Steps
Identify Stakeholders for this Release
The Development Team should know exactly which Stakeholder groups will benefit from the upcoming release. First, identify the Stakeholders for this release. Next, determine how each Stakeholder group is expected to benefit from the release based on the components that will be delivered to production.
Draft Communique for each Stakeholder Group
For each Stakeholder group, document the following: The features that will be deployed to production that those Stakeholders are expected to benefit from The business value that Stakeholder group will obtain from the feature set being released How, when, and where that Stakeholder group will be able to access the new functionality and what special credentials or permissions are required Any additional constraints or information that the Stakeholder group should be aware of, such as availability restrictions, geographical restrictions, server limitations, regulatory requirements, etc.
Provide Commiques to Deployment Manager
After drafting the communiques for each Stakeholder group, the Development Team should provide those drafts to the Deployment Manager. Typically, release communications are consolidated and released at the program level. The Deployment Manager and Deployment Engineers normally are responsible for ensuring that all release communications are consistent and concise. The Deployment Manager will determine the appropriate time to communicate information about the upcoming release to the appropriate Stakeholders.
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. EPF Copyright.