3.5 Other Team Members Take Care of Their Deliverables


3.5 Other Team Members Take Care of Their Deliverables

Severity levels are set. Companies typically have a grading system whereby anyone notifying IT of a bug can identify the severity of that bug. For instance, the severity rating can run from 1 to 5, with 1 being the worst. A severity 1 bug alerts the company that the bug crashes the system; a severity 5 bug may mean that the punctuation in a message is incorrect. QA, Help Desk, and IT should review the severity rating system and make sure they agree on what types of errors fall into which categories. An escalation path needs to be identified. This escalation path should include the functional areas that need to be notified and expected time for resolution. Even if your company has this grading system and escalation path in place, it is wise to review it and confirm that it meets the needs of the team.

First-draft documents are presented and reviewed. By the end of Phase 3, the first turn on the documentation should be complete. The documentation writer should have presented his or her first draft to each team member for review. The team members are responsible for confirming that the documentation meets the needs of their department and the Documentation Plan. The first-draft changes should be returned and the documentation updated before QA begins.

PRD is reviewed and updated. Business Development and the Project Manager should review the PRD and confirm that the needs of the end user , the company, and the industry have not changed. If it has been longer than six months since the Project Concept phase review the information presented in the Project Requirements Document needs to be reviewed. At a minimum the Internet should be searched and any new pertinent information should be brought to the team.

3.5 in a Nutshell

Around the time of the development review it is wise to take care of the following:

  • Have the team set severity levels for the project and identify escalation paths.

  • Review first-draft documents to ensure they are covering the correct material.

  • Business Development and the Project Manager should review the PRD and confirm that the needs of the end user, the company, and the industry have not changed.




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