5.4 The Beta Debrief and Release Plan Review

It is worthwhile for the team to debrief near the end of the beta. The team should discuss what they learned on the beta and how they will apply this experience to the release of the project. Areas of special interest should be: shipping, installing, training, and general use of the project. Beta sites are a snapshot of the general release of the project. The team should be asking if there are more efficient and cost-effective ways to ship, install, train, and support the users. The team should look at how difficult or easy it was to get the project to the users and get the users functioning on the project. Taking the time to discuss the process and ways customers can be better supported often saves time and money once the project is released; it also is a good indicator of the actual cost of maintaining the project. For example, the team may find that by conducting a weekly E-Learning course on how to use the application, support calls are cut in half and use of the application doubles.

By the end of beta the Project Manager must confirm that the Release Plan is ready for execution; that any hardware, software, and networking equipment needed for end users have been ordered and will be received on time; that the staging area and people needed to perform the staging are available, trained, and prepared to execute what is needed for the release; that all contracts have been signed; and that end users are prepared to receive the project.

5.4 in a Nutshell

Near the end of beta it is worthwhile for the team to debrief.

• The team should discuss what they learned so they can apply this experience to the release of the project.

• More efficient ways to install, train, or support users should be discussed.

  Tip  

  Taking the time now to discuss processes and methods to better support customers can save time and money once the project is released.