The influence of checklists and roles on software practitioner risk perception and decision-making

Keil, Mark; Li, Lei; Mathiassen, Lars; Zheng, Guangzhi

doi:10.1016/j.jss.2007.07.035

Cited by 51 publications

(38 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This may be an indication to the presence of lack of adequate knowledge among project managers. Research shows that project management knowledge limitation is one of the risks hampering project success (Keil et al, 2008;Mursu et al, 2003;Shaikh & Ahsan, 2014). It was also found common to perform risk identification, but not continue with risk analysis and development of mitigation or response plan.…”

Section: 3mentioning

confidence: 99%

Software Project Risk Management Practice in Ethiopia

Teklemariam

Mnkandla

2017

E J Info Sys Dev Countries

View full text Add to dashboard Cite

In a country like Ethiopia, where information and communication systems are in the early stage of development, software projects may face several challenges. Risk is one of the factors that challenges project performance, and even causes failure. Risk management helps project managers to control the effect of risks. However, risk management appears to be the least practiced component of project management. To help understand the software risk management practice in the developing countries (DC) context, this study explores the risk management practice of Ethiopian software projects. It also investigates the level of adoption of formal risk management models and which steps are included in the ad-hoc risk management exercise. Finally, it looks into the relationship between risk management practice and project success. We conducted a survey of 45 banks, insurance companies and United Nations agency offices in Addis Ababa, Ethiopia. In this study, a very low rate of application of formal risk management models was observed. We observed a different perception of risk management whereby only watching projects to see if any risks occur during implementation without performing risk identification and mitigation or response plan was considered as a risk management practice by project managers. It was also found that some project managers were not able to confidently tell whether risk management processes have taken place in the projects they manage.

show abstract

Section: 3mentioning

confidence: 99%

Software Project Risk Management Practice in Ethiopia

Teklemariam

Mnkandla

2017

E J Info Sys Dev Countries

View full text Add to dashboard Cite

show abstract

“…Risk mitigation in software development, which has been researched in both commercial and open source software projects for the last decade or so (Iversen et al, 2004;Keil et al, 2008;Kogut and Metiu, 2001;McGhee, 2007) can be properly addressed in the field with the help of special tools and procedures. One tool that has recently been developed is SPDX.…”

Section: Beyond the Bazaarmentioning

confidence: 99%

Collectivism, creativity, competition, and control in open source software development: reflections on the emergent governance of the SPDX<SUP align="right">®</SUP> working group

Kendall¹,

Kendall²,

Young³

2014

IJISAM

View full text Add to dashboard Cite

Abstract:For over a decade, we assumed that software developers had a choice between the cathedral and the bazaar: developers could choose to develop propriety software in a structural hierarchy of planned development, testing, and documentation or in a tumultuous and exciting, quick release open source marketplace. We are finding that these assumptions are no longer valid. Corporate members' participation in open source software development and greater attention to compliance with open source licenses has signalled the need for new metaphors for open source software design and development. In this study, we use participant observation and functional discourse analysis to determine which metaphors are useful and seek evidence for these metaphors in the emergent governance structure of the Software Package Data Exchange (SPDX ® ) working group, which is one of the important players in the future of open source development. We observed three governing structures for the SPDX working group: meritocracy, adhocracy, and family/republic and reflected back to the SPDX working group the need to pay greater attention to their governance structures to help in future strategic decisions. We conclude that open source developers now have a choice among collectivism, creativity, competition, and control. 126M. Germonprez et al.

show abstract

“…Furthermore (Keil et al, 2008), provided guidance on how to select members of review teams that help assure the quality of software project deliverables.…”

Section: C24: Ensuring That Quality-factor Deliverables and Task Analmentioning

confidence: 99%

A Comparison of Stepwise and Fuzzy Multiple Regression Analysis Techniques for Managing Software Project Risks: Analysis Phase

Elzamly

Hussin

2014

Journal of Computer Science

View full text Add to dashboard Cite

Risk is not always avoidable, but it is controllable. The aim of this study is to identify whether those techniques are effective in reducing software failure. This motivates the authors to continue the effort to enrich the managing software project risks with consider mining and quantitative approach with large data set. In this study, two new techniques are introduced namely stepwise multiple regression analysis and fuzzy multiple regression to manage the software risks. Two evaluation procedures such as MMRE and Pred (25) is used to compare the accuracy of techniques. The model's accuracy slightly improves in stepwise multiple regression rather than fuzzy multiple regression. This study will guide software managers to apply software risk management practices with real world software development organizations and verify the effectiveness of the new techniques and approaches on a software project. The study has been conducted on a group of software project using survey questionnaire. It is hope that this will enable software managers improve their decision to increase the probability of software project success.

show abstract

The influence of checklists and roles on software practitioner risk perception and decision-making

Cited by 51 publications

References 36 publications

Software Project Risk Management Practice in Ethiopia

Software Project Risk Management Practice in Ethiopia

Collectivism, creativity, competition, and control in open source software development: reflections on the emergent governance of the SPDX<SUP align="right">®</SUP> working group

A Comparison of Stepwise and Fuzzy Multiple Regression Analysis Techniques for Managing Software Project Risks: Analysis Phase

Contact Info

Product

Resources

About