SCENARIO AND RISK MANAGEMENT IN A PROJECT

Deekshita. S 1 Harshita Sivaramakrishna 1 and S. Rajeswari 2 . 1. Third Year Engineering Student Information Science and Engineering Department, New Horizon College of Engineering, Bangalore, India. 2. Senior Assistant Professor Information Science and Engineering Department, New Horizon College of Engineering, Bangalore, India. ...................................................................................................................... Manuscript Info Abstract ......................... ........................................................................ Manuscript History


Schedule plan collapse:-
The course of the schedule plan collapse is as listed-1.Ineffective charting of schedule plan considering the possibilities.2. Stake holders were given an unrealistic set of goals and time frames to the team.

Delivery Plan Collapse:-
The course of the delivery plan collapse is as listed-1.No documented inspection acceptance was obtained from the client.2. System test identified several bugs in generated file.3. Modification program had to be coded to rectify the bugs, which in turn resulted in incremental man hour requirement.4. The negotiation with the client for increment of staff broke down. 5. Due to lack of members, the delivery due was not tracked.Thus, the delivery plan collapsed.

Quality plan collapse:-
The course of the quality plan collapse is as listed-1.The implementation test did not encompass all the real jobs; it was carried out by sampling the weekly, monthly and annual jobs on the ordinary online.2. The test was coding by the Inspect Instructions of PC Cobol.The middleware caused Abed after a few hours of uninterrupted working.Abed Dump was obtained, and Dump identified the cause after analyzing.If implementation test encompassed all the real jobs, the Abed could be evaded.Without using Inspect, PC COBOL was re-coded as a recovery option.As a result, medical accounting jobs recovered, however, the timeline was long and the work came to a standstill.Thus, the quality plan resulted in collapse.

Application of pra to pm:-
In order to apply PRA to Project Management, it is essential to define the accident and differentiate the initiating event for the occurrence of the accident.In this scenario, the initiating event is the key factor that triggers the accident.Further, the accident scenario is enumerated with the help of event trees.In the end, the event probability of each scenario is calculated.

Merits
The credible merits of the application of PRA to PM are as given below-1.Accident scenarios can be enumerated using event trees.
2. The risk can be assessed with a dual approach.One, by combining the event probability of the scenario and two, by the degree of the influence.3. The risks can be accessed individually, for each scenario.

Issue of uncertainty:-
In a couple of previous sections, the scenarios of collapse of various plans, such as schedule plan, quality plan, staff plan and delivery plan were enumerated.
In addition to that, the scenarios with high event probability to fail were able to be extracted.However, the glitch is that, these event probabilities of the main collapse are only qualitatively presumed, i.e., they have elements of uncertainty.Consequently, the journal attempts to examine the uncertainty of the accident scenarios of the collapse of schedule plan, quality plan, staff plan and delivery plan.

Scenario of scheduling plan collapse
Scenario 1: After the submission of the in house design an oral acceptance was received from the client .No document inspection was received from the client.The bugs in the generated file are detected by the system test.To correct these bugs, increase in man-hours is required to create a modification program.This leads to added costs, increase in man hour and delayed delivery.The client breaks the negotiation.The contingency budget is not secure.