Best practices for managing risk in adaptive agile process

Khatri, Sunil Kumar; Bahri, Khushboo; Johri, Prashant

doi:10.1109/icrito.2014.7014759

Cited by 9 publications

(8 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to Table 15, all the respondents believe that Scrum has no specific activities for the practice of risk management, but the ceremonies of the framework allow the treatment of risks, agreeing with the opinion of other authors (Nelson et al, 2008;Nyfjord and Kajko-Mattsson, 2008;Khatri et al, 2014;Moran, 2014).…”

Section: Discussion Of Resultsmentioning

confidence: 75%

“…However, other authors believe that Scrum and other agile methodologies, in general, do not suggest specific activities to support risk management (Nelson et al, 2008;Nyfjord and Kajko-Mattsson, 2008;Khatri et al, 2014;Moran, 2014), and this management in Scrum is not as good as in traditional methodologies (Ravi et al, 2012). According to Ravi et al (2012), Scrum serves only for risk identification and it does not offer ways to analyze and manage them.…”

Section: Risk Management In Scrummentioning

confidence: 99%

“…It provides a set of good practices aimed at fast delivery value to the customers and can simplify the work process, reduce development time, and enhance organizational transparency (Thamhain, 2013). However, risk management, which can reduce uncertainty and increase the chances of success in software projects (Charette, 2005;SEI, 2010;Chowdhury and Arefeen, 2011;Wet and Visser, 2013), is conducted mostly in an implicit way in projects that use agile methodologies (Nelson et al, 2008;Nyfjord and Kajko-Mattsson, 2008;Khatri et al, 2014;Moran, 2014). Nyfjord and Kajko-Mattsson (2008) have performed a comparative analysis between traditional and agile risk management approaches.…”

Section: Introductionmentioning

confidence: 99%

“…r Characteristics of risk management-Agile methodologies do not explicitly suggest risk management processes (Nelson et al, 2008;Nyfjord and Kajko-Mattsson, 2008;Khatri et al, 2014;Moran, 2014).…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Risk management analysis in Scrum software projects

Tavares

Silva

Souza

2017

Int Trans Operational Res

View full text Add to dashboard Cite

One of the reasons for the failure of software projects is the absence of risk management procedures or its improper application. The adoption of Scrum in software projects is increasing. However, such approach does not specify risk management activities. This paper presents the results of a survey conducted using a qualitative approach to analyze how risk management is carried out in Scrum software projects. Consequently, we present risk management practices that achieved greater and lesser agreement among respondents and the literature, respectively. We found that risk management must be applied continuously in a feedback loop. Furthermore, Scrum projects must not have a high formal planning level, even for high‐risk ones. The research verified that risk management in Scrum is performed differently from its application in traditional approaches. The framework has native resources, but classic processes of risk management would be incorporated and adapted.

show abstract

Section: Discussion Of Resultsmentioning

confidence: 75%

Section: Risk Management In Scrummentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Risk management analysis in Scrum software projects

Tavares

Silva

Souza

2017

Int Trans Operational Res

View full text Add to dashboard Cite

show abstract

“…However, Risk Management, which can reduce uncertainty and increase the chances of success in software projects [9,10,11,12], is conducted in an implicitly way in projects which use agile methodologies [13,14,15]. Futhermore, risk management in agile projects needs to be improved without threatening the agility of projects [16].…”

Section: Introductionmentioning

confidence: 99%

Risk Management Analysis in Software Projects which Use the Scrum Framework

Tavares

Silva

Souza

2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Studies show one of the reasons for the failure of the software projects is the absence of Risk Management or its improper application. The adoption of Scrum Framework on software projects is increasing. However, the Scrum does not have specific Risk Management activities. In this scenario, this paper presents the results of a survey applied using qualitative approach, in order to analyze how Risk Management is carried out in software projects, which use Scrum. The research method adopted was the case study and the research instrument for data collection was developed based on scientific articles and the application of structured interviews. As a result, this paper presents Risk Management practices which achieved greater and lower agreement among respondents and literature. It was found that Risk Management must be applied continuously in a feedback loop. Furthermore, Scrum projects must not have a high formal planning level, even for the high risk ones. This result does not converge to the literature. The research verified that the Risk Management in Scrum projects is performed differently from its application on traditional methodologies. The framework has native resources, but the use of the classic Risk Management processes must be incorporated and adapted to Scrum.

show abstract