|
ID |
Risk Statement |
P |
L |
RE |
Date Identified |
Risk Mitigation Approach |
Who |
Date to finish |
Contingency Plan |
Trigger Value |
|
6 |
Some aspects
of the EDMS Strategy project (such as definition of
configurations) will be highly complex and therefore difficult
to manage. |
0.6 |
5.0 |
3.0 |
12/3/1997 |
1) Utilize
the Life-cycle model when applicable, including gate reviews and
applicable templates. 2) Conduct Conceptual Design workshop to
identify designs 3) Detail activities for each configuration in
the project schedule |
Dionne |
Ongoing |
Hold
planning meeting to define detailed tasks, schedules, and
resource requirements. Obtain resource commitments. |
Gate Review
for Design Phase will slip 3 weeks due to lack of WBS definition
or lack of resource commitment |
|
1 |
EDMS
Strategy project and EDMS Pilot projects will often be competing
for the same resources resulting in schedule impacts due to
resource constraints. |
0.6 |
5.0 |
3.0 |
12/3/1997 |
EDMS
Strategy and Pilot Projects will be closely coordinated.
Project Manager meets weekly Program Manager to discuss the
projects including schedule coordination. |
Dionne |
Ongoing |
Work with
Program Manager to identify additional resources necessary to
prevent unacceptable delays or revise schedule if acceptable. |
Gate Review
for Design Phase will slip 3 weeks due to lack of resources |
|
4 |
Roles/Responsibilities for some aspects of EDMS are not
well-defined with the IT organizations. This could lead to
schedule delays due to lack of commitment and delays in making
decisions. |
0.6 |
4.3 |
2.6 |
12/3/1997 |
Developing
Support Group charters to define roles/responsibilities during
EDMS projects and support of EDMS production installations. |
Durrett |
1/16/1998 |
Raise to
Director level for resolution. |
Gate Review
for Design Phase will slip 3 weeks due to lack of commitment/
ownership |
|
10 |
Lack of
general EDMS experience and product specific experience within
Entergy IT could result in schedule delays, inefficient use of
resources, and rework. |
0.5 |
5.0 |
2.5 |
12/3/1997 |
1)
Experienced individuals will be retained under contracts both
for this project and the EDMS pilot projects. 2) Product
specific training will be provided to key project and support
staff early in the project life-cycle. |
Dionne |
1/30/1998 |
Contract for
additional expertise and/or provide additional training. |
Determine
need by 2/15/98 |
|
11 |
Hardware
issues particularly related to multiple platforms may pose
contstraints to the projects resulting in schedule delays. |
0.3 |
6.3 |
1.9 |
12/3/1997 |
|
|
|
|
|
|
9 |
Tools are
not currently available for implementation of EDMS systems which
could result in delays or rework for the EDMS Strategy project
and Pilot projects. |
0.3 |
5.3 |
1.6 |
12/3/1997 |
|
|
|
|
|
|
12 |
Vacancies on
project staff could result in resource constraints that cause
schedule delays. |
0.3 |
5.3 |
1.6 |
12/3/1997 |
|
|
|
|
|
|
3 |
The EDMS
Program is not currently well-defined. This could result in
lack of defined direction in some areas which would result in
schedule impact and ineffective use of resources. |
0.5 |
3.0 |
1.5 |
12/3/1997 |
|
|
|
|
|
|
8 |
Lack of
define QA requirements for the EDMS Strategy project could
result in delays or rework. |
0.4 |
3.3 |
1.3 |
12/3/1997 |
|
|
|
|
|
|
2 |
Multiple
customers of the EDMS Program will attempt to drive the program
in different directions. This will make it difficult to define
requirements and identify configurations. |
0.2 |
4.0 |
0.8 |
12/3/1997 |
Monitor
situation through requirements gathering activity. Utilize the
services of a TQI facilitator to facilitate concensus and
decision making as necessary. |
Dionne |
4/1/1998 |
Escalate to
Program Manager and Director level if unable to resolve at
project level. |
Requirements
Gathering activity will slip three weeks. |
|
7 |
Budget
constraints may impact project resources resulting in schedule
impacts or lack of appropriate expertise. |
0.1 |
6.0 |
0.6 |
12/3/1997 |
|
|
|
|
|
|
5 |
Business
groups are not familiar with EDMS tools and therefore are not
sure how they can meet their needs. This will make it difficult
to accurately define requirements. |
0.1 |
1.0 |
0.1 |
12/3/1997 |
Overview of
system functionality and features will be provided to business
groups as part of the data gathering process. |
Durrett |
1/30/1998 |
Review
results of requirements gathering effort with Product Manager
and modify tasks as appropriate. |
Requirements
Gathering activity will slip three weeks. |
|
|
|
|
|
|
|
|
|
|
|
|