| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-FWdvN43s5ux00S-GVpDH-w" name="05_develop_release_communications,_g-LLEDHNEeC7j_IRiP-WPQ" guid="-FWdvN43s5ux00S-GVpDH-w" changeDate="2011-07-28T12:31:26.269-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| 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.
 |
| </p>
 |
| <p>
 |
| 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.
 |
| </p></mainDescription> |
| <sections xmi:id="_IAJWBuB-EeC1y_NExchKwQ" name="Identify stakeholders for this release" guid="_IAJWBuB-EeC1y_NExchKwQ"> |
| <sectionDescription>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.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAJWBeB-EeC1y_NExchKwQ" name="Draft communique for each stakeholder group" guid="_IAJWBeB-EeC1y_NExchKwQ"> |
| <sectionDescription><p>
 |
| For each stakeholder group, document the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The features that will be deployed to production that those stakeholders are expected to benefit from
 |
| </li>
 |
| <li>
 |
| The business value that stakeholder group will obtain from the feature set being released
 |
| </li>
 |
| <li>
 |
| How, when, and where that stakeholder group will be able to access the new functionality and what special
 |
| credentials or permissions are required
 |
| </li>
 |
| <li>
 |
| Any additional constraints or information that the stakeholder group should be aware of, such as availability
 |
| restrictions, geographical restrictions, server limitations, regulatory requirements, etc.
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_IAJWB-B-EeC1y_NExchKwQ" name="Provide commiques to deployment manager" guid="_IAJWB-B-EeC1y_NExchKwQ"> |
| <sectionDescription>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.</sectionDescription> |
| </sections> |
| <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.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
