|
A recent paper by the author, ‘Risk in Software Projects’ (in
Management Services, October 2001), briefly referred to risk
mitigation and its role in the risk management process.
Publication of this paper prompted considerable discussion and
requests for further information, particularly on software
projects in the design phase. My ongoing work into risk
management since that paper was originally published has
resulted in the development of a risk management tool/
methodology for software projects. This has also provided the
impetus to produce a more complete integrated methodology,
providing a basis for all the risk analysis material in this book.
In writing this book I was conscious of the need to bridge a gap
between current theory and what is good practice in the
management of software development projects. The book aims
to do this by focusing on what the practitioner needs to know
about risk in the pursuit of delivering software projects.
The book is structured into six chapters. Chapters 2–5 are
dedicated to a specific element of the risk model (or paradigm).
Chapter 1 sets the framework for Chapters 2–5. Each chapter
ends with a self-assessment checklist, and the subsequent
chapter starts with a recap on the previous one. Chapter 6 is
entirely devoted to a case study. Whilst I have attempted to
refrain from duplication, some duplication within chapters is
inevitable. However, I believe that this helps the reader by
reinforcing the points made in previous chapters.
Where appropriate to do so, I have used the terms ‘software
project manager’ and ‘project manager’ interchangeably
throughout the book. In essence, however, they are the same
entity.
Any book of this type can be improved upon and so I would
welcome any feedback you may have via the publisher. I trust
you enjoy reading this book. |
