5.3 A Monitored-Release Project

5.3 A Monitored -Release Project

Monitored releases are not needed if you have a hybrid beta, since you have had a wider audience test your project before its release. Sometimes hybrid betas are not feasible , however, and the team feels the beta period did not provide the extensive testing needed. Projects cannot stay in beta forever; teams need to release projects. When the team feels the project is stable but wants to maintain close control over the released project it is called a monitored release.

Sophisticated projects, those with interdependencies or requiring extensive training, may be good candidates for a monitored release. During beta, the team needs to decide how the project should be released. Should the project be sent out freely ? Does the team need to monitor the release? A monitored release is not related to quality but to scope. Some projects are so all-encompassing no beta site will ever be able to properly test the project. A monitored release provides the team with insight into who is receiving the project and how many people are using the project, so if a problem arises, the team knows the level of exposure.

Definition of a Monitored-Release Project

A monitored-release project is a project that has been released, but its monitored status means the team is still together and responsible for the project. This is a way to maintain visibility and funding on a complex project. If the team has questions about a user site, the monitored-release procedure provides the team with information so they can call the user before the project is shipped. In addition, the team may recommend that a knowledgeable employee is sent on-site if the project bogs down and the end user needs assistance or training. A monitored-release status allows the team to monitor which users receive a release, provides them insight into problems, and gives them the authority, responsibility, and budget to ensure the project works as specified.

Example flow of a monitored release for a sophisticated application that is targeted at a specific, well-defined audience:

1. User provides: name , address, contact, e-mail, and phone number when accessing the project.

2. At the team meeting the Project Manager presents this information to the team. The team decides if they need to call the user regarding any specific questions. The Project Manager is responsible for managing the monitored release process. The team decides who will be included on the phone call.

3. The team decides when to end the monitored period.

5.3 in a Nutshell

On complex projects the team might feel the beta period did not provide the extensive testing needed. Due to business pressures the project needs to be released.

• A monitored release allows projects with limited testing to be released.

• To expedite problems the beta team stays in place during a monitored release.

• A monitored release provides the team with greater insight into users who have received the monitored release project.