Managing risks in Norwegian Agile Software Projects: Project Managers´ perspective

Managing risks in Norwegian Agile Software Projects: Project Managers´ perspective

  IJETT-book-cover  International Journal of Engineering Trends and Technology (IJETT)          
  
© 2016 by IJETT Journal
Volume-41 Number-2
Year of Publication : 2016
Authors : Lubna Siddique, Bassam A. Hussein
DOI :  10.14445/22315381/IJETT-V41P211

Citation 

Lubna Siddique, Bassam A. Hussein"Managing risks in Norwegian Agile Software Projects: Project Managers´ perspective", International Journal of Engineering Trends and Technology (IJETT), V41(2),56-65 November 2016. ISSN:2231-5381. www.ijettjournal.org. published by seventh sense research group

Abstract
The purpose of this study is to understand the role of project risk management in agile software projects. To achieve the purpose, we conducted a qualitative study. We conducted interviews with agile practitioners working with agile projects in Norway´s software industry. Grounded theory was used to analyse the data. This study aims to study the similarities and dissimilarities between the project risk management process in agile software projects and waterfall software projects, as well as identify the strengths and weaknesses in the current practices being used in agile software projects. Interview results suggested that risk management in agile projects is being done in two ways. One way is adopting implicit risk management strategies, which include communication and collaboration, shorter iterations, frequent delivery, early feedback, and delivering complex parts first. The other way is called explicit risk management strategies, which are relative estimates, burn down charts, SWOT analysis, and risk matrix. Limitations with implicit risk management strategies are also discussed. At the end, guidelines on how to maximize the impact of the risk management process on project outcome are also presented.

 References

[1] Project Management Institute, inc. PMBOK, A Guide to the Project Management Body of Knowledge, 5th Ed., 2012.
[2] R. L. Van Scoy, Software Development Risk: Opportunity, Not Problem, Software Engineering Institute, Pittsburgh, PA CMU/SEI-92-TR-030, 1992.
[3] M. Paulk, “Agile Methodologies and Process Discipline”. Crosstalk (October 2002).
[4] M. Concha, M. Visconti and H. Astudillo, “Agile Commitments: Enhancing Business Risk Management in Agile Development Projects,” In: Concas, G., et al. (eds.) XP 2007, LNCS, 2007.
[5] M. J. Carr, S.L. Konda, I. Monarch, F.C. Ulrich and C. F. Walker, Taxonomy-based risk identification (No. CMU/SEI-93-TR-06). CARNEGIE-MELLON UNIV PITTSBURGH PA SOFTWARE ENGINEERING INST.
[6] N. Cerpa and J. M. Verner, “Why did your project fail?” Commun. ACM, vol. 52, no. 12, p. 130, Dec. 2009.
[7] D. Hillson, Managing risk in projects, Gower Publishing, Ltd., 2009.
[8] A. Moran, Agile Risk management, Springer Briefs in Computer Science. http://www.springer.com/series/10028, 2012.
[9] B.W. Boehm, "Software risk management: principles and practices," Software, IEEE 8.1, pp. 32-41, 1991.
[10] C. Chapman and S. Ward, Project risk management: processes, techniques and insights, John Wiley & Sons, Inc., 2003.
[11] M. T. Pich, C. H. Loch and A. D. Meyer, On uncertainty, ambiguity, and complexity in project management. Management science, vol. 48, no. 8, 1008-1023, 2002.
[12] J. Nyfjord and M. Kajko-Mattsson, “Commonalities in Risk Management and Agile Process Models”. In: ICSEA 2007, Cap Esterel France (August 2007).
[13] P. L. Bannerman, “Risk and risk management in software projects: A reassessment,” J. Syst. Softw., vol. 81, no. 12, pp. 2118–2133, Dec. 2008.
[14] A. J. Dorofee , J. A. Walker, C. J. Alberts, R. P. Higuera, and R. L. Murphy, Continuous Risk Management Guidebook. CARNEGIE-MELLON UNIV PITTSBURGH PA, 1996.
[15] K. Schwaber, Agile Project Management with Scrum. Microsoft Press, 2004.
[16] O.K. D. Lee and D. V. Baby, “Managing Dynamic Risks in Global It Projects: Agile Risk Management Using the Principles of Service-Oriented Architecture,” Int. J. Inf. Technol. Decis. Mak. vol. 12, no. 6, pp. 1121–1150, Nov. 2013.
[17] E. E. Odzaly, D. Greer and D. Stewart, Lightweight Risk Management in Agile Projects. In SEKE pp. 576-581, 2014.
[18] A. Albadarneh, I. Albadarneh and A. Qusef, “Risk management in Agile software development: A comparative study,” In Applied Electrical Engineering and Computing Technologies (AEECT), IEEE Jordan Conference, pp. 1-6. IEEE, 2015.
[19] L. Siddique and B. A. Hussein, “Practical insight about risk management process in agile software projects in Norway,” In Technology Management Conference (ITMC), 2014 IEEE International, pp. 1-4, IEEE, 2014.
[20] P. Advice, “Study design in qualitative research—2: Sampling and data collection strategies,” Education for Health, vol. 13, no. 2, pp. 263-271, 2000.
[21] B.G. Glaser, Emergence vs Forcing: Basics of Grounded Theory Analysis, Sociology Press, pp.16, 1992.
[22] B.G .Glaser and A. L. Strauss, “The discovery of grounded theory: Strategies for qualitative research.” Aldine, pp. 105-115, 1967.
[23] M. Birks and J. Mills, Grounded Theory: a Practical Guide, Sage Publications Limited, 2011.
[24] C. Marshall and G.B. Rossman, Designing qualitative research, Sage publications, 2014.
[25] L. Siddique and B. A. Hussein, “Grounded Theory Study of the Contracting Process in Agile Projects in Norway’s Software Industry,” The Journal of Modern Project Management, vol. 4, no. 1, 2016.
[26] L. Siddique and B.A. Hussein, “A qualitative study of success criteria in Norwegian agile software projects from suppliers’ perspective,” International Journal of Information Systems and Project Management, vol. 4, No. 2, pp. 63-79, 2016.
[27] L. Siddique and B. A. Hussein, “Grounded Theory Study of Conflicts in Norwegian Agile Software Projects: The Project Managers’ Perspective,” Journal of Engineering, Project, and Production Management, vol. 6, no. 2, pp. 120-135, 2016.
[28] M. E Hussein, S. Hirst, V. Salyers and J. Osuji, “Using grounded theory as a method of inquiry: Advantages and disadvantages,” The Qualitative Report, vol. 19, no. 27 , pp. 1-15, 2014.
[29] J.M. Corbin and A. Strauss, “Grounded theory research: Procedures, canons, and evaluative criteria,” Qualitative Sociology, vol. 13, no. 1, 1990.
[30] B. Glaser, Theoretical Sensitivity: Advances in the Methodology of Grounded Theory, Sociology Press, Mill Valley, CA, 1978.
[31] B. Glaser, Doing Grounded Theory: Issues and Discussions, Sociology Press, 1998.
[32] S. Georgieva and G. Allan, “Best Practices in Project Management through a Grounded Theory Lens,” Electronic J. Business Research Methods, vol. 1, pp. 43-52, 2008.
[33] B. Glaser, “Remodeling Grounded Theory,” Forum: Qualitative Social Research, vol. 5, no. 2, article 4, 2004.
[34] J. Breckenridge, Being person driven in a service driven organisation: a grounded theory of revisioning service ideals and client realities (Doctoral dissertation, Queen Margaret University), 2010.
[35] H. Thulesius, A. Hakansson, and K. Petersson, “Balancing: A Basic Process in End-of-Life Cancer Care,” Qualitative Health Research, vol. 13, no. 10, pp. 1353-1377 Tilley, N. 2000, Realistic, 2003.
[36] M. Cohn, Succeeding with agile: software development using Scrum, Pearson Education, 2010.
[37] M. Williams, J. Packlick, R. Bellubbi and S. Coburn (2007, August). “How We Made Onsite Customer Work-An Extreme Success Story,” In Agile Conference (AGILE), 2007, pp. 334-338, IEEE.
[38] M. Tomanek and J. Juricek, “Project risk management model based on PRINCE2 and SCRUM frameworks,” arXiv preprint arXiv:1502.03595, 2015.
[39] K. Schwaber and J. Sutherland, “The Scrum Guide: The definitive guide to Scrum: The rules of the game.” SCRUM.org, Jul-2013.
[40] S. Thomas, Agile Risk Management, Available: http://itsadeliverything.com/agile-risk-management, 2008.
[41] P. G. Smith, and R. Pichler, "Agile risks/Agile rewards." Software Development, vol. 13, no. 4, pp. 50-53, 2005.
[42] C. R. Nelson, G. Taran and L. de Lascurain Hinojosa, (2008, June). “Explicit risk management in agile processes,” In International Conference on Agile Processes and Extreme Programming in Software Engineering, pp. 190-201, Springer Berlin Heidelberg.
[43] D. W. Hubbard, The Failure of Risk Management: Why It`s Broken and How to Fix It, Wiley, 2009.
[44] X.N. Lu and Q.G. Ma, “Risk Analysis in Software Development Project with Owners and Contractors”, In: International Engineering Management Conference (October), 2004.
[45] B. Derfer, Introducing the Agile Risk Management Framework, Agile Six Applications, Inc., 2016.
[46] V. Ylimannela, A Model for Risk Management in Agile Software Development, Tampere University of Technology, 2011.
[47] K. Horvath. (2014) Risk Management in Agile and Waterfall Environments, available at: http://intland.com/blog/sdlc/risk-management-in-agile-and-waterfall-environments/ (assessed on 31-03-2016).
[48] M. Lant (2010), Five Simple Steps to Agile Risk Management, Available at: https://michaellant.com/2010/06/04/five-simple-steps-to-agile-risk-management/.
[49] B. Livingstone on (09/09/2015), Using Agile practices to manage project risk. Available at http://www.equinox.co.nz/blog/agile-practices-manage-project-risk.
[50] J. Nyfjord, “Towards integrating agile development and risk management,” 2008.

Keywords
Grounded theory, agile methods, risk management.