Categorizing Risks – Risk Breakdown Structure Risk identification Techniques - 2-3 page

_{Case Study: List of at least 10 risks in an appropriate risk register that includes:}

_{1.             Risk ID #} 

_{2.             Cause}

_{3.             Effect/Impact on triple constraints}

_{4.             Potential Risk Response}

_{5.             Risk Owner} 

_{See example file ( below)}

_{For each risk, create a Probability and Impact Scales}

refrences:

 Chapter 11.1 & 11.2 (PMBOK® Guide) + Chapter 11.5 & 11.6 (PMBOK® Guide)

formatt (12, double, times, 2-3 page)

-----------------------------------------------------------------------------------------------------------------

Example of a case Study:  Introducing the Organization

An organization that develops software for use in elementary schools has approximately 80 projects and programs currently underway to expand current product lines, keep up with newer technology used in schools, as well as process improvement initiatives in human resources, finance, and customer support. The current status of each project and program is tracked by the PMO, whether or not the project manager leading it reports directly to the PMO. The PMO monitors changes in the broad environment, and produces an aggregate, high- level performance report.  The PMO also helps organize creating and comparing business cases for potential new projects to facilitate the project and program selection process.

The CEO announced a new strategic initiative to expand quickly into the high school marketplace. Representatives from each of the functional areas have been asked to evaluate the impact of the new initiative on their functional groups. Here’s what they have submitted:

·       Finance: No major changes except adding new customers and revenue groups to our existing systems. We currently have a program to upgrade our ERP system with five projects underway that may interact with the proposed initiative.

·       Sales: Determine the changes needed to our geographically organized sales teams (hiring, training) and implement these changes. Supply new materials and training to the sales team.

·       Marketing: Need to develop new strategies, new promotions, new marketing materials and a new web site that is more interactive.

·       Software Development and Software Testing: No change assuming that the same software tools will be used. However, new staff will be hired and trained to accommodate the expected volume.

·       Customer Support:  Because customer support is organized by product group, a new section of 1^st level, 2^nd level and 3^rd level support will need to be developed for each new high school product group.

·       PMO: This new group of projects will have many synergies.

·       The other departments have not yet replied.