Product V2.0 Project Risks

(Last updated: Jan 27, 2002)

Open Risks

ID

Priority

Component/Issue

Manage the risk by

Responsible Person

9

High

First build of Component A is due on 1/18.  Some prep work can be done before this, but actual testing on the released product cannot start before this date.

 

 

 

5

High

Suite-level requirements document is too brief which could lead to misunderstandings of what the real requirements are

If disconnect occurs:

  1. Respect the mutual good intentions of the participants
  2. Escalate resolution to Frank and Ed

Frank and Ed.

7

High

Tiger project needs a Technical Writer; one of the resources committed to V2.0 might be partially allocated

Propose that new contractor be hired for this

Eylem, Frank

3

High

Possibility that resources will be tapped for other projects

 

Frank and Ed M.

1

Medium

General uncertainty of estimates

Divide tasks into small enough units, ensure that all tasks are identified, track progress against estimates

All

4

Medium

Unknown type and extent of bugs

Plan a reasonable amount of time for fixing bugs; carefully prioritize the bugs that are selected to be fixed.

Engineering managers and product managers

6

Medium

Aggressive schedule means unit testing will not be complete when code is turned over to QA

Unit testing will proceed in parallel with QA

Engineering managers


Some unscheduled requirements/tasks/activities that have affected the delivery dates include:

Component A:

Component B:

Component C:

Component D: