Risk Management in Software Development Projects

by McManus

• ISBN13: 9780750658676
• ISBN10: 0750658673
• Format: Paperback
• Copyright: 2003-11-18
• Publisher: Elsevier Science

Summary

Very few software projects are completed on time, on budget, and to their original specification causing the global IT software industry to lose billions each year in project overruns and reworking software. Research supports that projects usually fail because of management mistakes rather than technical mistakes. Risk Management in Software Development Projects focuses on what the practitioner needs to know about risk in the pursuit of delivering software projects. Risk Management in Software Development Projects will help all practicing IT Project Managers and IT Managers understand: * Key components of the risk management process * Current processes and best practices for software risk identification * Techniques of risk analysis * Risk Planning * Management processes and be able to develop the process for various organizations

Table of Contents

Computer Weekly Professional Series	ix
Preface	xi
Acknowledgements	xii
Book road map	xiii
1 The risk management process	1	(31)
1.1 Introduction to software risk management	1	(4)
1.1.1 Defining risk	3	(2)
1.2 Why do we need to manage risk in software development projects?	5	(2)
1.2.1 Cost	6	(1)
1.2.2 Assessment	7	(1)
1.3 Use of software risk management	7	(4)
1.3.1 Approach	9	(1)
1.3.2 Techniques	10	(1)
1.4 Objectives and goals of software risk management	11	(3)
1.4.1 Goals	12	(1)
1.4.2 Goals v. capability	13	(1)
1.5 Developing a software risk management strategy	14	(8)
1.5.1 Stages	14	(8)
1.6 Risk management paradigm	22	(3)
1.6.1 Risk paradigm	23	(2)
1.7 Developing the organization for software risk management	25	(2)
1.7.1 Cultural considerations	26	(1)
1.8 Risk management and litigation	27	(4)
1.8.1 The litigants	28	(1)
1.8.2 Litigation cases	28	(1)
1.8.3 Risk v. litigation	29	(2)
1.9 Self-assessment checklist	31	(1)
2 Discovering risk in software development projects	32	(30)
2.1 Recap on Chapter 1	32	(1)
2.2 Identifying software risk	32	(6)
2.2.1 Methods	33	(1)
2.2.2 Qualitative methods and techniques	34	(4)
2.3 Most common software project risks	38	(4)
2.3.1 Classification of risks	40	(2)
2.4 Risk taxonomy	42	(5)
2.4.1 Requirements	43	(1)
2.4.2 Design	43	(2)
2.4.3 Code and unit test	45	(1)
2.4.4 Integration and test	46	(1)
2.4.5 Communication, team compatibility and motivation	46	(1)
2.5 Risk mapping	47	(2)
2.5.1 Usefulness	48	(1)
2.5.2 Tools and packages	48	(1)
2.6 Risk statements	49	(2)
2.7 Risk reviews	51	(4)
2.7.1 Undertaking walkthroughs	51	(4)
2.8 Risk ownership and stakeholder management	55	(6)
2.8.1 Participation matrix	56	(1)
2.8.2 Importance	57	(1)
2.8.3 Stakeholder impact	58	(1)
2.8.4 Argument	59	(1)
2.8.5 Expectations	59	(2)
2.9 Self-assessment checklist	61	(1)
3 Risk assessment in software development projects	62	(34)
3.1 Recap on Chapter 2	62	(1)
3.2 Objectives and goals of software risk assessment	63	(1)
3.3 Approach to assessment	64	(1)
3.3.1 Key inputs	65	(1)
3.4 Risk assessment tools and techniques	65	(21)
3.4.1 Quantitative tools	66	(20)
3.5 Presenting the findings	86	(9)
3.5.1 Risk probability	87	(1)
3.5.2 Risk impact	88	(1)
3.5.3 Risk exposure	89	(1)
3.5.4 Constructing a risk matrix	89	(2)
3.5.5 Application problem	91	(4)
3.6 Self-assessment checklist	95	(1)
4 Planning risk mitigation strategies in software development projects	96	(26)
4.1 Recap on Chapter 3	96	(1)
4.2 Risk planning	97	(2)
4.2.1 Risk planning objectives	97	(2)
4.2.2 Pre-planning meeting	99	(1)
4.3 Best practice in risk planning	99	(6)
4.3.1 Properly defined standards and adherence to such standards	99	(2)
4.3.2 Continuous improvement in the practice of risk management	101	(1)
4.3.3 Competent personnel trained in the use of risk management practices	102	(2)
4.3.4 Risk and software metrics	104	(1)
4.4 Risk management tools	105	(5)
4.4.1 Expert tools in risk management	107	(3)
4.5 Risk mitigation strategies	110	(6)
4.5.1 Avoidance strategies	111	(1)
4.5.2 Transfer strategies	112	(2)
4.5.3 Reduction strategies	114	(1)
4.5.4 Retention strategies	114	(2)
4.6 Formulating and implementing risk management plans	116	(5)
4.6.1 Why create a risk plan?	116	(1)
4.6.2 Key steps in formulating the risk plans	117	(1)
4.6.3 Product breakdown structure	118	(1)
4.6.4 Costing the plan	119	(1)
4.6.5 Implementing the risk management plan	120	(1)
4.7 Self-assessment checklist	121	(1)
5 Monitoring risk in software development projects	122	(18)
5.1 Recap on Chapter 4	122	(1)
5.2 Developing a process for monitoring risk	123	(4)
5.2.1 Safeguards	124	(1)
5.2.2 Verification	125	(1)
5.2.3 Monitoring of third party risk	125	(1)
5.2.4 Key deliverables	126	(1)
5.2.5 Macro risk indicators	126	(1)
5.3 Formulating a project risk database /risk register	127	(5)
5.3.1 The risk database (and register)	128	(1)
5.3.2 Benefits	129	(1)
5.3.3 Key roles	130	(1)
5.3.4 Responsibility	131	(1)
5.4 Managing and tracking risk	132	(4)
5.4.1 The project office	133	(1)
5.4.2 Risk audits	134	(2)
5.5 Risk support tools	136	(3)
5.5.1 Cost and benefit	138	(1)
5.6 Self-assessment checklist	139	(1)
6 Case study	140	(17)
Appendix A Glossary of risk terminology	157	(4)
Appendix B Risk management software tools	161	(2)
Subject reading	163	(4)
References	167	(2)
Index	169