Home
 
Information
Sources

 
Training &
Seminars

 
About
Btt

 


 

 

Page 8 of 8

Risk Management: 
A practical toolkit for identifying, analysing and coping with Project Risk
 

References

DION93: Raymond Dion, "Process Improvement and the Corporate Balance Sheet",

IEEE Software, July 1993, Pages 28-35.

DION95: Raymond Dion, Tom Haley, Blake Ireland and Ed Wojtaszek of Raytheon Electronic Systems, “The Raytheon Report: Raytheon Electronic Systems Experience in Software Process Improvement”, November 1995, SEI web-site,

http://www.sei.cmu.edu/products/publications/95.reports/95.tr.017.html/.

This is an important update of earlier reports.

GILB88: Tom Gilb, “Principles of Software Engineering Management”,

Addison-Wesley, 1988, 442 pages. ISBN 0-201-19246-2. See particularly Chapter 6, Estimating the Risk (reproduced in Boehm, Software Risk Management, IEEE CS Press, 1989 page 53).

GILB93: Tom Gilb and Dorothy Graham, “Software Inspection”, Addison-Wesley, 1993, ISBN 0-201-63181-4, 5TH printing 1998, 471 pages.

This book covers the Defect Detection Process and the Defect Prevention Process, as well as giving sample Rules to check by, defined processes and a well defined set of Glossary terms to aid quantification and comparison. It is a next-generation Inspection, with hundreds of larger and smaller improvements over initial Inspection practices.

GILB98: Tom Gilb, Various papers and manuscripts on www.gilb.com.  The manuscripts include:

  • ‘Requirements-Driven Management using Planguage’ (1995-6)
  • 'Evolutionary Project Management’ (1997)
  • ‘Requirements Engineering Language’ (1998).

HALL98: Elaine M. Hall, “Managing Risk: Methods for Software Systems Development. SEI Series in Software Engineering”, Addison Wesley Longman, USA. (enq.orders@awl.co.uk) , £31.95, 1998, ISBN 0-201-25592-8, 374 pages.

This book is impressive and contains a lot of useful detail and original thought. Anyone interested in risk will enjoy and learn from the book as I did. It does not however deal with most of the subjects in this paper {specification languages, impact estimation, inspections, evolutionary delivery}. This in no way detracts from the book’s favorable recommendation. It does tackle ‘quantified objectives’ much better than other texts.

MAY96: Elaine L. May and Barbara A. Zimmer, “The Evolutionary Development Model for Software”, Hewlett-Packard Journal, August 1996, Vol. 47, No. 4, pages 39-45.

The author was at HP in 1989 on a project team who were taught early versions of the Planguage method. The article is full of practical advice and case studies gleaned from ten major projects in eight HP divisions. It must be strongly recommended to anyone interested in the practical implementation of Evo in a project and especially in an organization for many projects. See also article by Todd Cotton in same issue on Evo.

HP Journal subscription free to qualified individuals: Write Distribution Manager, HP Journal, M/S 20BH, 3000 Hanover Street, Palo Alto, CA, USA-94304, or Email: hp_journal@hp_paloalto-gen13.om.hp.com. HP Journal is available on World Wide Web at “http://www.hp.com/hpj/Journal.html”. (Warning HP may have moved this site, but you can get to the new site from here)
 

©Tom Gilb 2005
 

The "How to find out more" Department
For more on the subjects covered in this article, use these links...

About the author: Tom Gilb

Related articles: Rich Requirement Specifications, Quantifying Qualitative RequirementsBasic Design Principles

Books: for indepth coverage of the techniques in this article, and the Planning Language 'Planguage', take a look at  Competitive Engineering, Principles of Software Engineering Management and Software Inspection.

The comprehensive glossary of terms and concepts accompanying the Competitive Engineering book can be accessed online at
CE Glossary (N. America) or CE Glossary (outside N. America).

Web links: for comprehensive coverage of Risk Management in business.

For general background: Btt principles

Learn more - attend a seminar or training course: more...

To raise questions or discuss the subjects further...  questions.
 

 

Back to: Projects Implementation     Back (previous): Page 7 of 8     End
 

Copyright © Biness Transition Technologies Ltd 2004.  A

ll Rights Copyright © Business Transition Technologies Ltd 2006.  All Rights Reserved.