Search results

The main objective of the paper is to develop a risk management framework for software development projects from developers' perspective.

This study uses a combined qualitative and quantitative technique with the active involvement of stakeholders in order to identify, analyze and respond to risks. The entire methodology has been explained using a case study on software development project in a public sector organization in Barbados.

Analytical approach to managing risk in software development ensures effective delivery of projects to clients.

The proposed risk management framework has been applied to a single case.

Software development projects are characterized by technical complexity, market and financial uncertainties and competent manpower availability. Therefore, successful project accomplishment depends on addressing those issues throughout the project phases. Effective risk management ensures the success of projects.

There are several studies on managing risks in software development and information technology (IT) projects. Most of the studies identify and prioritize risks through empirical research in order to suggest mitigating measures. Although they are important to clients for future projects, these studies fail to provide any framework for risk management from software developers' perspective. Although a few studies introduced framework of risk management in software development, most of them are presented from clients' perspectives and very little effort has been made to integrate this with the software development cycle. As software developers absorb considerable amount of risks, an integrated framework for managing risks in software development from developers' perspective is needed.

The purpose of this paper is to review the content, contributions and subsequent developments of the seminal paper by Barry Boehm, “A spiral model of software development and enhancement” written in 1988. The relationships of this paper to software development, agile projects, real options and present practice are put into perspective.

Basically an essayist approach is taken. First, the contents of Boehm's paper are reviewed and then associated with subsequent developments.

Review of the paper as published represents a documentation of cutting‐edge software development as it existed at the time. Fundamentally it suggests the viability of a non‐linear, customer‐influenced, development approach.

This basic approach illustrated in the spiral model of course has found its way into complex project approaches and management.

This paper follows the lines of increasing attention to classics, which is the purpose of this special issue of the journal. In particular, attention is called to the transition of thought on projects and project management from supplier‐oriented, linear processes to customer/client‐influenced, non‐linear ones.

The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team to reduce cost and improve schedule for re-engineering projects in global software development environment.

The system dynamics technique is used for simulation model construction and policy run experimentation. The experts from Indian software outsourcing industry were consulted for model construction, validation and analysis of policy run results in both co-located and distributed software development environment.

The study results show that there is a drop in the overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule.

The study found that there could be substantial cost saving for re-engineering projects with a loss of project schedule when an appropriate onsite–offshore combination is used. The quality and productivity drop, however, were rather small for such combinations. The cost savings are high when re-engineering work is sent to offshore location entirely after completion of requirement analysis work at onsite location and providing training to offshore team in business knowledge The research findings show that there is potential to make large cost savings by being flexible in project schedule for re-engineering projects.

The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment.

The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in global software development environment.

Discusses problems related to software engineering task maintenance. Argues that since many scientists and practitioners have regarded maintenance as divorced from development, it is not properly embedded in project models. Relates four case studies. Looks at the range of maintenance tasks and strategies. Proposes a change of perspective that would make maintenance part of development. Advocates methods, tools and techniques as possible means of overcoming the problematic situation.

This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.

This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.

The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.

Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.

The purpose of this paper is to gain insights about the applicability of Lean principles in software industry along with the Lean implementation issues.

Exploratory case studies have been carried out in five software companies. Data were collected by observation and semi-structured interviews with project managers. In this paper, case organizations are categorized as product vs project software development (SD) organization.

It is found that although Lean principles are being adopted in SD projects, application of all Lean principles is not visible. This research reveals that value and flow are more relevant in SD organizations, while value stream, pull and perfection are not conspicuous.

This paper would prove invaluable to lean practitioners and researchers to gain knowledge in lean SD. The paper puts forward the key issues that should be addressed for successful adoption of lean in SD. This study set out to determine the practitioners’ perception of the applicability of lean principles in SD projects. It provides a sound basis for further empirical research on adoption of lean principles in SD organizations.

This study aims to empirically investigate the relationship between different global software development (GSD) challenges (management, process, social, technical and environmental challenges) and software project success. Further, the study examines the moderating role of total quality management (TQM) between the relationship of GSD challenges and success of software projects.

Using two field studies, the authors collected data form software developers working in globally distributed teams. In study 1 (n = 194), relationship of different dimensions of GSD challenges (management, process, social, technical and environmental challenges) and project success was examined. In study 2 (n = 138), moderating role of TQM was examined on the relationship of GSD challenges and project success.

The results of study 1 indicate that there is a negative relationship between all dimensions of GSD challenges and project success. Findings of study 2 confirmed that TQM practices moderate the negative relationship between GSD challenges and project success.

The findings of the study provide guidelines to the project managers of software industry to mitigate GSD challenges using TQM practices.

Study adds in the literature of TQM, GSD challenges and project success by (1) empirically investigating the relationship between different GSD challenges and software project success and (2) by examining the moderating role of TQM practices on relationship of GSD challenges and project success in global software development industry.

The purpose of this study is to identify a typology of procurement contracts in the context of software development projects that allows firms to align design flexibility with design uncertainty at the project level. The theoretical lenses of contract theory and software engineering are used to explain why the five archetypes in the proposed typology provide gradually increasing levels of design flexibility and to develop hypotheses about the associations between design flexibility and a set of project cost dimensions.

The hypotheses are tested with objective contractual data from 270 software development contracts entered into by a leading international bank over a period of three years.

Data analysis confirms the existence of the proposed typology and shows that design flexibility is negatively associated with control and positively associated with coordination, trust, duration and price.

Although the findings are based on the contracting practices of a single, albeit sophisticated, organization, they shed light on the ability of firms to align flexibility with uncertainty at the onset of new projects by taking advantage of nuanced contractual mechanisms to produce a broader set of contractual archetypes.

This paper is the first in the outsourcing literature to analyze a nuanced contractual typology in software development projects through the perspectives of both contract theory and software engineering.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

The paper has three purposes: the first is to provide a deeper understanding of the ideology and work practices of free and open source software development, the second to characterize the free software movement as a new type of computerization movement and the third to present a conceptual diagram and framework with an analysis showing how the free software computerization movement has evolved into an occupational community.

Qualitative data were collected over a four year period using a virtual ethnography in a study of free and open source software development and, in particular, a study of a free software community, GNUenterprise, located at www.gnuenterprise.org, which has the goal of developing a free enterprise resource planning software system.

It is concluded that the ideology of the free software movement continues to be one of the factors which mobilize people to contribute to free and open source software development. This movement represents a new type of computerization movement which promotes the investment of time in learning a new software development process instead of investment of money in the acquisition and use of new technology.

The research findings are limited by a detailed study of only one free software development project.

This paper is of significance to software developers and managers of firms who wish to incorporate free and open source software into their companies.

This research presents an original conceptual diagram and framework for how computerization movements have emerged into an occupational community.