RISK MITIGATION PLAN - DRAFT

2/10/97

MJY TEAM

Introduction

The purpose of this risk mitigation plan is to outline the risks that have been identified by the team as having highest probability to impact our schedule. These risks have been categorized as High, Medium and Low.

Top Ten Risk List

The following list contains the Top Ten risks the MJY group has identified during the initial requirements development phase of our program. Each item is also prioritized as being of (L)ow, (M)edium or (H)igh risk.

• (H) WEB Site capacity/stability - Will we run out of space for our WEB site?

• (H) Staffing - All WEB site development is being performed by one person.

• (M) Access to GMU - Will we be able to get the necessary permissions for all of our site requirements, i.e. posting documents, chatrooms, etc.?

• (M) Interactive chatroom - This feature requires further investigation to access complexity and to finalize requirements.

• (M) Volatility of external links - How stable are the links we are using?

• (M) Schedule

• (L) User interface - This feature requires further investigation to access complexity and to finalize requirements.

• (L) Requirements "creep"

• (L) Availability of other search engines - Identify search engines available and their reliability.

• (L) Support for all WEB browser technology

Minimizing the Risk

WEB Site capacity/stability

1. Make use of each group member's available disk space by use of links.
2. Minimize risk associated with a central source by having a backup of our site on another machine.
3. Investigate other site possibilities.
4. Have each MJY team member investigate whether their work site offers some space for installing a Software Management WEB site.

Access to GMU

1. Investigate other site possibilities.
2. Have each MJY team member investigate whether their work site offers some space for installing a Software Management WEB site.

Staffing

1. Require training for at least X other team members in development.
2. Assign back-up developers. Make sure they are always current on the status of the page and understand the update procedures so they can easily move into Development if the developer becomes ill, drops the course, goes on travel, etc.

Interactive chatroom

1. Investigate other site possibilities.
2. Have each MJY team member investigate whether their work site offers some space for installing a Software Management WEB site.

User interface

1. Assign to specific team members to investigate.

Requirements "creep"

1. Make use of the CCB
2. Set a firm date for finalizing requirements.

Availability of other search engines

1. Assign to specific team members to investigate.

Volatility of external links

1. Place a disclaimer on the page about the currency of the links.
2. Indicate "last update" date on the page.
3. Assign each MJY team member in rotation each week the responsibility of verifying that the page links are current.

Support for all WEB browser technology

1. Assign to specific team members to investigate.

Schedule

1. Publish weekly status reports.
2. For each of the team roles assign a back-up person(s). They can help any team member who is having problems meeting the schedule or deliverables.
3. Schedule weekly meetings after class to specific review status, schedule and assign action items.