Goal and Risk Factors in Offshore Outsourced Software Development from Vendor's Viewpoint

Islam, Shareeful; Joarder, Md. Mahbubul Alam; Houmb, Siv Hilde

doi:10.1109/icgse.2009.54

Cited by 24 publications

(22 citation statements)

References 9 publications

(16 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This paper contributes to integrate Goal-driven Software Development Risk management Model (GSRM) [8,9] for managing software development risk as part of Requirements Engineering (RE). The model considers goals relating to project success beyond schedule, budget, and quality and recognises the importance of motivating project stakeholders in particular customer/user to take active part during the development.…”

Section: Introductionmentioning

confidence: 99%

Integrating risk management activities into requirements engineering

Islam¹,

Houmb

2010

2010 Fourth International Conference on Research Challenges in Information Science (RCIS)

Self Cite

View full text Add to dashboard Cite

Abstract-Software projects are often faced with unanticipated problems caused by e.g. changes in the development environment resulting in delays or threatening the ability of the project to succeed. Managing these uncertainties is a challenging task at all phases of the development, but nevertheless crucial in controlling schedule and costs. Therefore software development risks need to be controlled as early as possible. As software development risks are not merely of technical nature it is equally important to tackle non-technical risks. The paper presents a goal-driven software development risk management model (GSRM) that takes a holistic view on development, taking both technical and non-technical development components into consideration. The focus of the paper is on how to integrate GSRM and particularly the holistic risk perspective into requirements engineering. GSRM effectively identifies and makes explicit the critical project goals (for arriving at a successful project) and the risk factors that may obstruct these goals. GSRM also helps in planning how to employ control actions for mitigating risks and by that increase the ability to meet project goals. The integrated requirements engineering risk management model has been applied to an on-going development project in a low-cost development environment (Bangladesh). The result showed it to be relatively trivial to integrate the model into requirements engineering activities and that the model did indeed contribute to the overall project success.

show abstract

Section: Introductionmentioning

confidence: 99%

Integrating risk management activities into requirements engineering

Islam¹,

Houmb

2010

2010 Fourth International Conference on Research Challenges in Information Science (RCIS)

Self Cite

View full text Add to dashboard Cite

show abstract

“…In our previous studies, only offshore software development projects were investigated where customers/ users are located in different locations [IJH09,IHMFJ09,IH10]. But the present study context is a software project for a local customer.…”

Section: Comparison Of the Study Results With Previous Researchmentioning

confidence: 99%

“…This section presents the survey results [IJH09] of investigating goals related to project success and threats which obstruct the goals in offshore-outsourced software development from Vendors' Viewpoint. This study was conducted using the Delphi survey process.…”

Section: Study 1: Goal and Risk Factors In Offshore Outsourced Softwamentioning

confidence: 99%

“…Goal-driven risk management model from holistic perspective: This research contributes an integrated modeling framework for software development risk management, called Goal-driven Software Development Risk Management Model(GSRM) [IJH09,Isl09]. The framework is comprised of a conceptual model, analysis techniques and a methodology to systematically identify, model, analyze and control risks to attain the project specific goals.…”

Section: Research Contributionmentioning

confidence: 99%

See 1 more Smart Citation

Software development risk management model

Islam

2009

Proceedings of the Doctoral Symposium for ESEC/FSE on Doctoral Symposium

Self Cite

View full text Add to dashboard Cite

Every software project by its inherent nature is unique and contains significant numbers of uncertainties from various perspectives such as time-to-market, budget and schedule estimation, product deployment or maintenance. If failing to control these uncertainties, it imposes potential risks not only during the development phases but also throughout the life cycle of the product. Software risk management is an effective tool to control these risks and contributes to increase the likelihood of project success. Risk management needs to be integrated as early as possible from a holistic perspective into the development. However a comprehensive risk management practice is not always possible due to resource problems, more emphasize on budget and schedule constraints and difficulties to concretely estimate the benefit of risk management.This thesis proposes a Goal-driven Software Development Risk Management Model (GSRM) that explicitly integrates into the requirements engineering phase. The integration provides an early warning of potential problems so that both preventive and corrective actions can be undertaken to avoid the causes of project failure. The framework is comprised of four layers, i.e., goal, obstacle, assessment and treatment, that support the identification, assessment, treatment and documentation of risks in relation to project-specific goals. GSRM is implemented in active on-going software development projects to empirically evaluate its usefulness, particular advantages and limitations in an industrial context. The results show that goaldriven approach is suitable for risk management and risk management is well integrated into requirements engineering phase. It is not always necessary to rank budget and schedule related goals and risk factors at the highest priority for risk management. At the early stage of the project risk factors related to estimation, project management, project scope, requirements, change management and human (i.e. customer/user and practitioner) and at the later stage risk factors related to user satisfaction and product usage are more frequent and severely affect meeting the project goals. If project risk factors are beyond the control of a project manager and project development environment, it is difficult to control the risks. The results conclude that early risk management practice is necessary and GSRM contributes to this direction for a successful project outcome. ZusammenfassungJedes Software-Entwicklungsprojekt ist einzigartig und geprägt von schwer planbaren Einflussfaktoren, wie time-to-market oder Budget, aber auch von Einflüssen resultierend aus der Integration und der Wartung. Die Beherrschung dieser Einflussgrößen ist unabdingbar für die Minimierung der Risiken während der Entwicklung als auch während des gesamtem Software-Lebenszyklus.

show abstract

“…The work of Islam et al in [7] and that of Gupta and Sadig in [8] proposed a quantitative model for risk control while the Alves et al in [9] proposed a qualitative risk analysis model focus on offshoring. We followed the idea of quantitative risk assessment but instead of creating our own rules in assessing the risks, we used Capability Maturity Model Integration (CMMI) as a guideline and attempted to apply it to offshoring risks.…”

Section: Introductionmentioning

confidence: 99%

A Risk Assessment Tool Using a CMMI Quantitative Approach

Choetkiertikul¹,

Kula²

2012

IJET

View full text Add to dashboard Cite

Abstract-A notable purpose of offshoring is to gain competitive advantages in software development business. While offshoring offers great opportunities, it also creates a new trend of threats in software development due to differences in culture, languages, time zones, and development processes deployed. Maximizing the profits of the offshoring relies on strong remote project management skills including remote risk analysis. It is important that potential risks should be detected promptly and there should be quantitative indicators that can help to precisely monitor risks in a remote manner. In that view, we present an offshoring risk assessment tool which uses our formally defined CMMI quantitative approach. This tool is implemented on IBM JAZZ platform to enable quantitative risk monitoring and assessment for application life cycle support.Index Terms-Offshoring development, software risk monitoring and assessment, quantitative CMMI.

show abstract

Goal and Risk Factors in Offshore Outsourced Software Development from Vendor's Viewpoint

Abstract: Abstract

Cited by 24 publications

References 9 publications

Integrating risk management activities into requirements engineering

Integrating risk management activities into requirements engineering

Software development risk management model

A Risk Assessment Tool Using a CMMI Quantitative Approach

Contact Info

Product

Resources

About