Using risk management to balance agile methods: A study of the Scrum process
Authors:
- 1 November 2015
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 49-54
Abstract
This study seeks to answer three main questions: How can Risk Management be used to effectively balance an agile method (particularly Scrum)? What are the benefits or limitations that could be encountered during the application of Risk Management as a successful procedure during Scrum projects? What other processes can be applied by organizations to effectively manage their risks during Scrum projects? The mixed methods of interviews and focus group discussions with Scrum/Agile practitioners and experts in three UK IT sectors were conducted to investigate the farragoes of assumptions on how the Scrum process in particular deals with risks. Results of data analysed suggest that most organizations using Scrum do not implement any risk strategy for their projects under the assumption that the `agile aspect of Scrum' will mitigate risks, however, all respondents agreed that this would most likely introduce other risks that could impact the objectives of the project.Keywords
This publication has 15 references indexed in Scilit:
- Project Risk Management Model Based on PRINCE2 and Scrum FrameworksInternational Journal of Software Engineering & Applications, 2015
- Agile Risk Management2014
- A Step‐by‐Step Guide to Using Secondary Data for Psychological ResearchSocial and Personality Psychology Compass, 2011
- A survey study of critical success factors in agile software projectsJournal of Systems and Software, 2008
- Commonalities in Risk Management and Agile Process Models2007
- Project Management in Plan-Based and Agile CompaniesIEEE Software, 2005
- Using risk to balance agile and plan- driven methodsComputer, 2003
- Focus GroupsAnnual Review of Sociology, 1996
- Qualitative Research: Introducing focus groupsBMJ, 1995
- Software risk management: principles and practicesIEEE Software, 1991