5.5 Beta Presentation


Once beta sites have reviewed the project, the team can present their beta findings to executive staff (see Figure 5.1).

click to expand
click to expand
click to expand
click to expand
click to expand
click to expand
click to expand
click to expand
click to expand
click to expand
Figure 5.1: Beta Presentation

Page 1: Cover Page. This document should be for controlled distribution and list the names of all the people attending and receiving the review handout. The cover page should have the project name , the phase, and the date.

Page 2: Agenda. List major deliverables for this phase, the team members who will be presenting, and the time allotted for each presentation. Agenda items for a Phase 5 review may include introduction, general program status, team overview, and issues and risks.

Page 3: Phase 5 ”Beta Project Status. Review the action items that have been created or completed in a Phase 5:

  • Project announcement and worldwide rollout plan implemented

  • Release Plan for project in place and ready for execution

  • User documentation, training, and logistical support in place

  • Help Desk prepared to support user volume

  • A projection of QA s confidence on the readiness of the project to enter general availability is established

Page 4: Review Phase 4. Review the action items from Phase 4 to see if they are complete. List the item and its status.

Page 5: Integrated Schedule. For Phases 4 and 5, list the start and completion date for Development, Documentation, QA, Beta, Release, and maintenance.

Page 6: Updated Development Costs. For Phases 4 and 5, list Business Development, IT, QA, Documentation, and Help Desk contracted costs.

Page 7: Contracted Costs Update. For Phases 4 and 5, list the hardware costs, the software costs, and the networking costs, as well as the personnel costs to develop, stage, and support the project, any transportation costs, and sustaining costs to support.

Page 8: Beta Status. List user name, date installed, date upgraded, beta feedback meeting, and beta sign-off.

Page 9: Bug Report. List the outstanding bugs not fixed or those with no action plan in place, the number of bugs with a severity of 1 to 3, the software confidence level as of today, and the QA confidence level for First User Ship date (FUS date).

Page 10: Team Status Cover Sheet. The pages that follow highlight the team deliverables that have been created by team members.

Page 11: Project Manager. Update integrated schedule, projected costs, and Release Plan readiness.

Page 12: Business Development and Communications. Any changes in the market and Announcement Plan readiness will need to be annotated.

Page 13: IT. List the deliverables created by IT, such as changes between Phase 4 and Phase 5 reviews, whether there are severity 1 or 2 bugs open , IT s involvement with monitoring and supporting beta sites, readiness to release project, readiness of sustaining IT to take over responsibility of the project.

Page 14: Documentation. List the deliverables created by Documentation, such as incorporate beta markups and reissue beta version of the manuals for beta shipment and IT review. Documentation should note if the beta version of the manuals and help files is ready for release.

Page 15: QA. List the deliverables created by QA, such as final testing of bugs fixed during beta, QA test report complete, and confidence rating of the project.

Page 16: Help Desk. List the deliverables created by Help Desk, such as final project support plan and education training plan for additional Help Desk people.

Page 17: Training. Training created and ready for users.

Page 18: Issues and Risks. For this phase, list issue, owner, risk, impact, and status.

Page 19: Executive Session. Executive sign-off, executives note any action items for the team and agree to let the program move to the next phase.

5.5 in a Nutshell

By the end of beta:

  • Documentation is completed.

  • The team has signed off on its quality.

  • The project announcement is ready or in progress.

  • There are no known severity 1 or 2 bugs.

  • The beta sites have signed off on the project.

  • The Release Plan is in place and ready.

  • The Project Manager updates the financial and release information.

  • The phase review is presented to executive staff.




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