Skip to main content

Outlining a Risk-Driven Development Model (RDD)

  • Chapter
  • First Online:
Trends in Communication Technologies and Engineering Science

Part of the book series: Lecture Notes in Electrical Engineering ((LNEE,volume 33))

  • 508 Accesses

Abstract

On the surface, agile and risk management process models seem to constitute two contrasting approaches. Risk management follows a heavyweight management approach whereas agile process models advocate a lightweight engineering one. Despite this, a merge between those two is possible. This chapter suggests a Risk-Driven Development model (RDD), a model integrating risk management with agile development process models. It first identifies commonalities in these two process models. It then investigates the state of practice of integrating risk management with software development in 37 software organizations. The results of these two steps provide feedback for outlining the RDD model. The RDD model itself was evaluated by 10 software practitioners.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 169.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Abrahamsson P. et al., Agile Software Development Methods: Review and Analysis. VTT Electronics/ Oulu University, 2002.

    Google Scholar 

  2. Beck K., Extreme Programming Explained: Embrace Change.2nd Ed. Addison-Wesley, Upper Sadle River, NJ, 2004.

    Google Scholar 

  3. Boehm B., “A Spiral Model of Software Development and Enhancement”, IEEE Computer, Vol. 21 (5), 1988, pp. 61–72.

    Google Scholar 

  4. Boehm B.,“Software Risk Management: Principles and Practices”. IEEE Software, Vol. 8 (1), 1991, pp. 32–41.

    Article  Google Scholar 

  5. Carr M.J. et al., “Taxonomy-Based Risk Identification”. SEI Technical Report CMU/SEI-93-TR-006 ESC-TR-93-183, SEI/CMU, Pittsburg, PA, 1993. URL: http://www.sei.cmu. edu/pub/documents/93.reports/pdf/tr06.93.pdf, Accessed March 2007.

  6. Charette R., Software Engineering: Risk Analysis and Management. McGraw-Hill, New York, NY, 1989.

    Google Scholar 

  7. Charette R., The Decision is in: Agile vs Heavy Methodologies (2001). Cutter Consortium, Vol. 2 (19) http://www.cutter.com/content/ project/fulltext/updates/2001/epmu0119.html. Accessed in October 2007.

  8. Cohn M., Agile Estimating and Planning. Pearson Education, Upper Saddle River, NJ, 2006.

    Google Scholar 

  9. Hulett D.T., “Key Characteristics of a Mature Risk Management Process”. Proceedings of the European Project Management Conference/PMI Europe 2001, 2001.

    Google Scholar 

  10. 1040, “IEEE 1540 Standard for Lifecycle Processes-Risk Management". IEEE, New York, NY, 2001.

    Google Scholar 

  11. IEEE Software, Managing Risk” (special issue). IEEE Software, Vol. 14 (3), 1997.

    Google Scholar 

  12. Institute of Risk Managment, Association of Insurance and Risk Managers and National Forum for Risk Management in the Public Sector, “A Risk Management Standard”. UK, 2002. URL: http://www.theirm.org/ publications/PUstandard.html. Accessed February 2007.

  13. Kontio J., “Risk Management in Software Development: a Technology Overview and the Riskit Method”. Proceeding of the International Conference on Software Engineering, 1999.

    Google Scholar 

  14. Mahnic V. and Drnovscek V., “Agile Development with Scrum”. Proceedings of the European University Information Systems Conference, 2005.

    Google Scholar 

  15. McBreen P., Software Craftsmanship – The New Imperative, Addison-Wesley, New York, 2002.

    Google Scholar 

  16. Nyfjord J. and Kajko-Mattsson M., Commonalities in Risk Management and Agile Process Models, In Proceedings, IEEE International Conference on Software Engineering Applications, IEEE Computer Society Press: Los Alamitos, CA, 2007.

    Google Scholar 

  17. Nyfjord J. and Kajko-Mattsson M., Degree of Agility in Pre-Implementation Process Phases, In Proceedings, International Conference on Software Process, Lecture Notes in Computer Science, Springer Verlag, 2008.

    Google Scholar 

  18. Nyfjord J. and Kajko-Mattsson M., Communicating Risk Information in Agile and Traditional Environments, In Proceedings, 33rd Euromicro Conference on Software Engineering and Advanced Applications, IEEE, Computer Society Press: Los Alamitos, CA, 2007.

    Google Scholar 

  19. Nyfjord J. and Kajko-Mattsson M., Agile Implementation Phase in Two Canadian Organizations, In Proceedings, IEEE Australian Software Engineering Conference, IEEE Computer Society Press: Los Alamitos, CA, 2008.

    Google Scholar 

  20. Nyfjord J. and Kajko-Mattsson M., Software Risk Management: Practice contra Standard Models, In Proceedings, International Conference on Research Challenges in Information Science, IEEE, Computer Society Press: Los Alamitos, CA, 2008.

    Google Scholar 

  21. Nyfjord J. and Kajko-Mattsson M., Integrating Risk Management with Software Development: State of Practice, In: Proceedings, IAENG International Conference on Software Engineering, BrownWalker Press, Boca Raton, USA, 2008.

    Google Scholar 

  22. Nyfjord J. and Kajko-Mattsson M., Outlining a Model Integrating Risk Management and Agile Software Development, In Proceedings, 34rd Euromicro Conference on Software Engineering and Advanced Applications, IEEE, Computer Society Press, Los Alamitos, CA, 2008.

    Google Scholar 

  23. Padayachee K., “An Interpretive Study of Software Risk Management Perspectives”. Proceedings of the Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists on Enablement Through Technology, 2002.

    Google Scholar 

  24. Poppendieck M. and Poppendieck T., Lean Software Development – An Agile Toolkit, Adidison-Wesley, New York, 2003.

    Google Scholar 

  25. Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBoK), 3rd Ed. ANSI/PMI 99-001-2004, Project Management Institute, Newton Square, PA, 2004.

    Google Scholar 

  26. Ropponen J. and Lyytinen K., “Components of software development risk: how to address them? A project manager survey”. IEEE Transactions on Software Engineering, Vol. 26(2), 2000, pp. 98–112.

    Article  Google Scholar 

  27. Schwaber K., Scrum Development Process. Proc. of Conference on Object-Oriented Programming, Systems, Languages and Applications, 1995.

    Google Scholar 

  28. Schwaber K., The Enterprise and Scrum. Microsoft Press, Redmond, WA, 2007.

    Google Scholar 

  29. ScrumMethodology, Scrum Methodology: Incremental, Iterative Software Development from Agile Processes. Rev. 0.9. Advanced Development Methods Inc., 2003.

    Google Scholar 

  30. Sliger M., “Relating PMBoK Practices to Agile Practices” (Part 3 of 4). URL: http://www. stickyminds.com/sitewide.asp?Function=edetail&ObjectType=COL&ObjectId=11133& commex=1#4993. Accessed February 2007.

  31. Software Engineering Institute/Carnegie Mellon University, “Risk Management Overview”. URL: http://www.sei.cmu.edu/risk/. Accessed February 2007.

  32. Sommerville I., Software Engineering, 7th Ed. Addison-Wesley, Reading, MA, 2006.

    Google Scholar 

  33. Standards Australia and New Zealand, “Australian/New Zealand Standard Risk Management AS/NZS 4360:2004”.3rd Ed. Standards Australia/New Zealand, Sydney/Wellington, Australia/New Zealand, 2004.

    Google Scholar 

  34. Westfall L., “Software Risk Management”. The Westfall Team, 2001. URL:http:// www.westfallteam.com/Papers/risk_management_paper.pdf. Accessed February 2007.

  35. Williams R. et al., “Software Risk Evaluation (SRE) Method Description (Version 2.0)”. Technical Report CMU/SEI-99-TR-029, SEI/CMU, Pittsburg, PA, 1999.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Mira Kajko-Mattsson .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Springer Science+Business Media B.V

About this chapter

Cite this chapter

Kajko-Mattsson, M., Nyfjord, J. (2009). Outlining a Risk-Driven Development Model (RDD). In: Wai, PK., Huang, X., Ao, SI. (eds) Trends in Communication Technologies and Engineering Science. Lecture Notes in Electrical Engineering, vol 33. Springer, Dordrecht. https://doi.org/10.1007/978-1-4020-9532-0_21

Download citation

  • DOI: https://doi.org/10.1007/978-1-4020-9532-0_21

  • Published:

  • Publisher Name: Springer, Dordrecht

  • Print ISBN: 978-1-4020-9492-7

  • Online ISBN: 978-1-4020-9532-0

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics