Risk Management

Risk ID

Risk Area

Impact

Likelihood

Priority (Impact * Likelihood)

Status (Open or Complete)

1

No specific experience with ASP.NET

7

2

14

Open

2

No specific experience with ADO.NET

9

2

18

Open

3

No specific experience with .NET Frame Work Web services

8

1

8

Open

4

No specific programming experience with C# or .NET

10

1

10

Complete

5

No specific experience programming with using a web service to interface an MS SQL 2000 database

9

1

9

Open

6

No specific programming experience at all

10

0

0

Complete

7

No specific XML data experience

8

1

8

Complete

8

No specific XML schema experience

7

1

7

Complete

9

No specific SQL database experience

10

0

0

Complete

10

Unexpected hardware of software purchase required with no funds available

6

0

0

Open

11

Catastrophic Hardware failure

10

2

20

Open

12

Catastrophic Software failure

10

1

10

Open

Mitigation Plans

Preventive Action(s)

Contingent Action(s)

Trigger(s)

Risk #1 Is being worked on diligently as we speak by reading and researching a book called “Essential ASP.NET with Examples in C#.”

Use Java Script in the absolute worst case scenario.

Spending any more than just one day trying to do the prototype for this will be a great indicator.

Risk #2 Is being worked on diligently as we speak by reading and researching another book called “Pragmatic ADO.NET Data Access for the Internet World.”

At present I don’t have a viable back plan for this since no other DBMS data access layer that I know of or have experience with would knowingly work flawlessly with this project. I did receive a “Deklarit” License for .NET not long ago for another DBMS. but haven’t looked into it yet.

When comes time to start coding the data base schema that I create with knowingly no knowledge of how to.

Risk #3 Research how best to implement the SaveData() and GetData() methods for each of the components.

Conduct prioritized emergency research and problem resolution steps.

For Risk #1 the trigger is spending more than 4 working days on a web-service-related problem.

Risk #4 is already mitigated with evidence to show for it.

Complete the summer session web services class

Conduct prioritized emergency research and problem resolution steps.

For Risk #3 the trigger is spending more than 4 working days on a web-service-related problem.

Risk #6 is already mitigated with evidence to show for it.

Complete the summer session web services class

Conduct prioritized emergency research and problem resolution steps.

For Risk #5 the trigger is spending more than 4 working days on a web-service-related problem.

Complete the summer session web services class

Conduct prioritized emergency research and problem resolution steps.

For Risk #6 the trigger is spending more than 4 working days on a web-service-related problem.

Risk #10 is already mitigated with evidence to show for it.

Keep hardware and software in good working order.

Draw on available credit line to fulfill the current hardware of software need.

For Risk #8 the trigger is an unexpected hardware or software failure.

Keep hardware in good working order

Draw on available credit line to fulfill the current hardware need.

For Risk #9 the trigger is an unexpected hardware failure.

Keep software in good working order

Draw on available credit line to fulfill the current software need.

For Risk #9 the trigger is an unexpected software failure.

Update: 11/24/04

Over the last month since I last evaluated risks, I had at large and what appears to be five major risks that halt or otherwise sabotage the progress of my Puzzle – 3D Style project:

ASP.NET inexperience: Over the last month I’ve had time to read in detail five chapters out of this book, and with several much appreciated pointers by Scott and my web services instructor Patrick Cauldwell, I’ve been able to acquire “enough-to-be-dangerous” knowledge to begin construction of quality ASP.NET pages as required. I will down grade the likelihood score from a 4 to a 2.

ADO.NET inexperience: Over the last month I’ve had time to read in detail five chapters our of this book. I briefly skipped ahead to the part that talked about how Xml and Web Service high integration support was built in with ADO.NET from the ground up. I was thrilled to read this, and as a result of studying Xml and Web Service for what will be six month, I may say with confidence that I will down grade the likelihood score from a 4 to a 2.

Web Services to Database: Of course this will obviously involve ADO.NET to interface with the project data with all calls being done asynchronously. I’ve spent a considerable amount of time thinking about this, but it looks as though it is as simple as using something that derives from the class library Stream to specify where and how to save to a database. From what I’ve learned from doing my research, I will down grade this risk from a 2 to a 1.

Unexpected Hardware Failure: Since I started this project, my wife’s car irrevocably broke down, exceeding it’s own value with the repair cost, forcing us to unexpectedly replace her vehicle to get around. As a result of this and quitting this job I currently have for good in less than seven months, I have cancelled my retirement contributions with Qwest. The extra funds should be enough to provide for an additional car payment as well as hardware expenses for this project. I will down grade the likelihood for this risk from a 3 to a 2.

Unexpected Software Failure: There are only two possible causes for this: 1) A virus, of which has been dramatically mitigated with the combination of Symantec Norton Antivirus 2003 and Symantec Norton Internet Security 2003 both with full subscriptions through 2005, and 2) A critical tool that was unaccounted for, of which we both know is completely improbably since I accounted for every that we’d need for this project last summer including resources. Please note the all the software and data is backup onto a separate computer under a complete separate power supply and motherboard. I will down grade the likelihood of this risk from a 3 to a 1.