Chapter 6: Phase 6 - Release


˜ ˜All mankind is divided into three groups: those that are immovable , those that are movable, and those that move.

”Benjamin Franklin

6.1 Release Overview

After the beta sites sign off on the quality of the project, and the team completes its phase review, the project is released. Release entails the actions taken to make the project available to users. This may be as simple as enabling a link on a Web site or as complex as setting up a staging area where equipment is received, configured, and given to employees . For Release to begin, the team has decided on the scope of the Release ” monitored or normal. Help Desk states they are ready to take over full support of the project, and user training is ready. Communications confirms that advertising, collateral , and the press information are ready and being delivered. The role of each project team involved in Phase 6 is listed below.

IT

IT is the functional area responsible for programming, managing, and integrating the project s hardware and software. They are also responsible for defining, designing, and developing a project, as well as for conducting its initial testing and fixing any errors before it is released. IT is the key member on the project team and needs to be available to provide technical information both written and verbal to all members of the team.

Communications

Communications is the functional area responsible for all communications inside and outside of the company. Smaller companies do not need a separate communications person for internal projects; the Project Manager will handle all the internal corporate communication. Larger companies with offices scattered around the country or around the globe will need a person to provide communications to end users. If the project being developed will be made available to people outside the company, the communications person will need to interact with public relations, advertising, industry analysts, and other outside agencies.

Business Development

The Business Development person is responsible for directing and driving the project, for analyzing the industry and the competition, and for understanding the user. Business Development works with all areas of the company to make sure the project is focused on the user and is presented in the best possible light.

Project Manager

The Project Manager s responsibility is to make sure each member of the team understands his or her interdependencies. The Project Manager facilitates communications among departments as well as manages processes and confirms that the deliverables within each stage of the project life cycle have been met. When deliverables slip, it is the responsibility of the Project Manager to escalate this information and to facilitate resolution. In smaller companies, the Project Manager s duties usually incorporate those of Business Development and Communications.

Quality Assurance

Quality Assurance (QA) is responsible for defining, designing, developing, and implementing a test plan. QA tests the project to confirm that it meets the design specifications outlined in the Design Document and the PRD. QA uses the user manuals and help files developed by Documentation to ensure that they correctly explain how to install and use the project and identify how errors are to be handled. QA is responsible for managing the user test procedures defined in the Beta Plan and for confirming that bugs have been fixed.

Help Desk

Help Desk is responsible for defining, designing, and developing a detailed plan that articulates how the company will support a project after it is released. The Support Plan defines how Help Desk personnel are trained, how users will access help, how bugs will be tracked and fixed after release, what training will be available to end users, and how updates and fixes will be sent to users.

Documentation

Documentation is responsible for defining, designing, and developing all the documentation required to install, support, and answer any questions a user may have regarding a project. Documentation defines what publications will be produced in the Doc Plan; these may include online help, E-Learning courses, or manuals. Documentation works closely with IT to develop these documents and works closely with QA to ensure that documents are appropriate for end users.

Training

Training is responsible for developing and providing training courses to employees, partners , and customers. These may be on-site classes or training over the Web.

6.1 in a Nutshell

Release entails the actions taken after the beta for the project to be made available to users.

  • This may be as simple as enabling a link on a Web site or as complex as setting up a staging area where equipment is received, configured, and given to employees.

  • Help Desk is ready to take over support of the project.

  • Communications is ready to announce the project.

The following groups are responsible for releasing the project:

  • IT

  • Communications

  • Business Development

  • Project Manager

  • Quality Assurance

  • Help Desk

  • Documentation

  • Training




Effective IT Project Management
Effective IT Project Management: Using Teams to Get Projects Completed on Time and Under Budget
ISBN: B000VSMJSW
EAN: N/A
Year: 2004
Pages: 105
Authors: Anita Rosen

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net