Journals / PressAcademia Procedia / 2016 / Cilt: 2 - Sayı: 1

MANAGING INTERACTING SOFTWARE PROJECT RISKS

Pages
427–433
Publication Date
2016-06-01
DOI
—
🏛️Bibliographic metadata and full text access for this article are provided via DergiPark.
DergiPark Record ↗
✨

AI Summary & Key Takeaways

AI Insight
⚡ TL;DR(Too Long; Didn't Read)

By integrating risk based project management into a software development process, coordination of all activities in a comprehensive manner would be possible with a special emphasis on interacting risks

📌 3 Key Takeaways

🎯
Objective & Hypothesis:Managing risks in a software project can be challenging.
📊
Key Findings & Data:Appropriate strategies should be developed for managing imminent risks in a timely manner.
💡
Conclusion & Impact:By integrating risk based project management into a software development process, coordination of all activities in a comprehensive manner would be possible with a special emphasis on interacting risks
🔬Design:Research Article
📍Scope:Comprehensive Sample
⚙️Variables:Communication · iterative models · risk analysis

Abstract

Managing risks in a software project can be challenging. There are many risk categories including communication risks, project planning risks, technical risks, budget risks, scheduling risks, legal risks, ethical risks, operational risks, security risks, and personnel risks that require timely attention. Potential risks should be identified, analyzed and evaluated. Appropriate strategies should be developed for managing imminent risks in a timely manner. This paper advocates a strategy that assigns a special role to communication risk, because it interacts with other risks in a way that may allow its coupling with most other risks and changing their effects. Interacting risks may have to be studied at a higher level with special attention to communication risk, because it could be considered as a super-risk. In order to get best results with the current state of knowledge, a team of risk analysts may provide early warnings about potential risks that are then further studied in interaction contexts for developing appropriate management strategies. By integrating risk based project management into a software development process, coordination of all activities in a comprehensive manner would be possible with a special emphasis on interacting risks

🔖

Cite This Article

DEY, P. P., KHAN, M., AMİN, M., SİNHA, B. R., BADKOOBEHİ, H., JAWAD, S., ANY, L. A. (2016). MANAGING INTERACTING SOFTWARE PROJECT RISKS. PressAcademia Procedia, Cilt: 2 - Sayı: 1, 427–433. https://ajindex.com/articles/842767

📄 Full Text PDF Viewer

📄

PDF görüntüleyici hazırlanıyor...

References (14)

  1. Armour, P. G., (2015). The Business of Software: Thinking Thoughts, Communications of the ACM, (Vol.58, No. 10, pages 32-34).
  2. Barros, M., Werner, C. & Travassos, G., (2004). Supporting Risks In Software Project Management, Journal of Systems and Software, Volume 70, Issues 1–2, Pages 21–35.
  3. Boehm, B., (1991), Software Risk Management: Principles and Practices, IEEE Software 8,1, pages 32-41.
  4. Braude, E., & Bernstein, M., (2011). Software Engineering: Modern Approaches, (2nd Edition), John Wiley & Sons. Carmel, E., & Agarwal, R., (2001). Tactical Approaches For Alleviating Distance In Global Software Development, IEEE Software, Vol. 18, No. 2, pp. 22-29.
  5. Charette, R.N., (1989). Software Engineering Risk Analysis And Management, Intertext, New York. Chemuturi, M. & Cagley Jr., T., (2010), Software Project Management: Best Practices, Tools and Techniques. J. Ross Publishing, Plantation, Florida. Drucker, P., (2008). Management (Revised Edition), Harper Collins, New York. Espinosa, J. A., Slaughter, S. A., Herbsleb, J. D., Kraut, R. E., (2007). Team Knowledge and Coordination in Geographically Distributed Software Development, Journal of Management Information Systems, Vol. 24, Issue 1, 2007.
  6. Gantt, H., (1919).
  7. Organizing for Work, Harcourt, Brace, and Howe, New York. Gries, D., (1981). The Science of Programming. Springer, 1981.
  8. Gulla, J., (2012).
  9. Seven Reasons IT Projects Fail, IBM Systems Magazine, Retrieved August 8, 2015 from: http://www.ibmsystemsmag.com/power/Systems-Management/Workload Management/ project_pitfalls/ Harrison, M. A., Ruzzo, W. L. & Ullman, J. D., (1976).
  10. Protection in Operating Systems, Communications of the ACM, Vol. 19, No.8, Pages 461–471.
  11. Holmström, H., Ó., Conchşir, E., Ågerfalk, P.J., & Fitzgerald, B., (2006). Global Software Development Challenges: A case Study on Temporal, Geographical and Socio-Cultural Distance, ICGSE2006,
  12. Costao do Santinho, Florianopolis, Brazil, Oct 19, 2006.
  13. Humphrey, W., (1989).
  14. Managing the Software Process, Addison-Wesley, Reading, Mass. Jalote, P. (2002). Software Project Management in Practice. Boston: Addison Wesley. Jones, C., (1994). Assessment and Control of Software Risks, Prentice-Hall, Englewood Cliffs, N.J. Jones, C., (1998). What it Means to be ‘Best in Class’ for Software, Capers Jones, Software Productivity Research, Inc. www.spr.com. Keil, M., Cule, P. E., Lyytinen, K., & Schmidt, R.C., (1998). A Framework for Identifying Software Project Risks, Communications of the ACM, Vol.41, No. 11., pa