Risk Management Post Analysis: Gauging the Success of a Simple Strategy in a Complex Project

Abstract

The authors implemented a simple risk management system within a communications management system (CMS)—a large software development and system integration project. This case study reviews results regarding the use of the system in terms of the evolution of the priority of several risks tracked over the life of the project. The case study also draws conclusions about risk categories common to other high-technology projects. The system's efficacy for risk management within the project, its potential for reuse in similar projects, and its scalability to projects of different sizes and scopes also are reviewed.

Keywords

risk management large projects post analysis software project management

Get full access to this article

View all access options for this article.

References

Abramovici

(2000). Controlling scope creep. PM Network, 14(1), 44–48.

Hall

E.M.

(1998). Managing risk: Methods for software systems development. Reading, MA: Addison-Wesley.

McConnell

(1996). Rapid development. Redmond, WA: Microsoft Press.

Pressman

R.S.

(1993). A manager's guide to software engineering. New York: McGraw-Hill.

PMI Standards Committee. (1996). A guide to the project management body of knowledge. Upper Darby, PA: Project Management Institute.

Royer

P.S.

(2000). Risk management: The undiscovered dimension of project management. Project Management Journal, 31(1), 6–13.

xwave. (2000). xWay project management fundamentals: Risk management guidelines V1.0. St. Johns, Newfoundland and Labrador, Canada.