Risk Identification in software industry

Exclusive forum for iZenBirdge PMP® clients
kshitij_y
PMP
Posts: 229
Joined: Wed Dec 11, 2013 9:39 am

Risk Identification in software industry

Postby kshitij_y Mon Jan 27, 2014 6:58 am

While doing Risk Identification in software industry , Which are the factors taken care into consideration,
Update me with point which we can use as basic to create Risk Break Down Structure. or Eg. of Risk Break down structure while handing software project.
namita
Super Member
Super Member
Posts: 502
Joined: Wed Dec 11, 2013 10:25 am

Re: Risk Identification in software industry

Postby namita Mon Jan 27, 2014 12:49 pm

Risk identifications are very tricky because its difficult to visualize the risk before its inception. This is the reason in practical scenarios, identification is driven mostly by opinion from experts and historic similar projects.

There are different techniques like documentation analysis, assumptions analysis and information gathering etc.. In all of these techniques people involved in such activities are important. Basic consideration which we always need to remember is what are our project constraints and what kind of risks it can arise during project..
namita
Super Member
Super Member
Posts: 502
Joined: Wed Dec 11, 2013 10:25 am

Re: Risk Identification in software industry

Postby namita Mon Jan 27, 2014 1:08 pm

Risk Breakdown Structure is just a hierarchical representation. Basic of creating RBS is categorizing risk. Question should be why we do categorization and how do we do it?
Why - Categorization helps in visualizing the impact on defined categorizes which helps in routing the effort towards controlling the risks. E.g. after risk categorization we identified that all the work packages under planning category is showing more vulnerability. This will help in better control and effort utilization
How - Basis of categorization is driven by the fact of need. E.g. an organization is very strong in its processes, but they have taken up a project in new domain. In that case categorization should not be on Initiation, planning etc.. rather it should be on the basis of its domain components or e.g. on technical, non technical, internal, external types of categories
Ideally speaking a categories based on how critical is risk (major, minor, fatal etc) and its likelihood of occurrence also can be represented in hierarchical form and named as RBS
kshitij_y
PMP
Posts: 229
Joined: Wed Dec 11, 2013 9:39 am

Re: Risk Identification in software industry

Postby kshitij_y Tue Jan 28, 2014 4:30 pm

Dear Namita

Can you share any standard Checklist or RBS for IT industry.

Regards
Kshitij Yelkar

Return to “PMP® Queries and Tips”

Who is online

Users browsing this forum: No registered users and 5 guests