Following on from my previous post on thinks to look at when reviewing a Change; you might find it useful to have a template for Change communications. The following is a sample communication template:
SERVICE A
Release Note
Release Date: Sunday 3rd August 2008
1. Overview.. 1
Overview
This document outlines the content of the release at a high level. The intended readership is for Volunteer testers, and those people that wish details about what is changing in the TBC system.
The general format is; Change or Known Error Number, followed by a brief summary of the enhancement / issue, then some detail about how it has been addressed.
Change 1234 – Service A Enhancements
This SERVICE A release is to include new …
The following data items have been added:
etc, etc
Subscribe to:
Post Comments (Atom)
Microsoft Teams 101
One of the things I've been asked about most this week has been how to use Teams for meetings. Teams is basically Microsoft's replac...
-
Following on from my previous post on things to look at when reviewing a Change, it is important to investigate risk to ensure that stakehol... -
As promised, here is my take on the Release note (and yes, of course it’s pink!!) It includes the title of the release, the audience, any... -
So here's the thing. No one likes major incidents; by their very definition they are the serious stuff. But there is something that’s...
No comments:
Post a Comment