scholarly journals Suppliers’ software development project start-up practices

2017 ◽  
Vol 10 (4) ◽  
pp. 880-896
Author(s):  
Helena Merikoski ◽  
Paula Savolainen ◽  
Jarmo J. Ahonen
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Cycle Phase ◽  
Development Projects ◽  
Content Type ◽  
Business Context ◽  
Software Development Project ◽  
Business Goals ◽  
Start Up

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

Bounded becoming: insights from understanding projects in situation

2012 ◽  
Vol 5 (3) ◽  
pp. 345-363 ◽  
Author(s):  
Viviane Sergi
Keyword(s):  
Project Management ◽  
Software Development ◽  
Design Methodology ◽  
Development Project ◽  
Process Ontology ◽  
Content Type ◽  
Software Development Project ◽  
Specific Practice ◽  
The Moment ◽  
Over Time

PurposeThe purpose of this paper is to suggest a situated conception of projects, in order develop finer understanding of how these endeavors emerge and unfold over time. The author proposes that these understandings should be rooted in a process ontology, conceive action as situated and focus on actual practices as they are performed by all project actors. Taken together, these dimensions can renew how one views and approaches projects and their management.Design/methodology/approachThe paper is illustrated with examples taken out of a study of a software development project, conducted in the ethnographic tradition.FindingsThe examples expose how a specific practice, planning, was accomplished differently depending on the moment and was affected by different circumstances and constraints. The paper also discusses how preferring a processual worldview is especially befitting projects. As endeavors instigated to create or to make something happen, projects are perpetually changing and in movement; it is therefore relevant that their conceptualization takes fully into consideration their intimate nature.Originality/valueThe originality and value of the paper lie in the combination of perspectives, which can be both useful in theorizing projects differently, and in enhancing practitioners' reflexivity. This combination, it is argued, can address a wide array of issues in the context of projects, can favor localized reflection on project management prescriptions and tools, and can help practitioners to sharpen their sensitivity to their own practice.

A study of software development project cost, schedule and quality by outsourcing to low cost destination

2016 ◽  
Vol 29 (3) ◽  
pp. 454-478 ◽  
Author(s):  
Debasisha Mishra ◽  
Biswajit Mahanty
Keyword(s):  
Software Development ◽  
Development Project ◽  
Dynamics Simulation ◽  
Software Project ◽  
Design Work ◽  
Project Cost ◽  
Content Type ◽  
Software Development Project ◽  
Study Results ◽  
Testing Work

Purpose – The purpose of this paper is 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 so as to reduce project cost and improve schedule in a global software development (GSD) environment for software development project. Design/methodology/approach – This study employs system dynamics simulation approach to study software project characteristics in both co-located and distributed development environments. The authors consulted 14 experts from Indian software outsourcing industry during our model construction and validation. Findings – The study results show that there is a drop in 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. Research limitations/implications – The implication of the study is that the project management team should be careful not to keep high percentage of manpower at offshore location in distributed software environment. A large offshore team can increase project cost and schedule due to higher training overhead, lower productivity and higher error proneness. In GSD, the management effort should be to keep requirement analysis and design work at onsite location and involves the offshore team in coding and testing work. Practical implications – 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. Originality/value – The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in GSD environment.

Identification of Patterns for the Formation of Software Development Projects Teams

2010 ◽  
Vol 1 (3) ◽  
pp. 69-80 ◽  
Author(s):  
Margarita André Ampuero ◽  
María G. Baldoquín de la Peña ◽  
Silvia T. Acuña Castillo
Keyword(s):  
Software Development ◽  
Delphi Method ◽  
Development Project ◽  
Project Teams ◽  
Psychological Characteristics ◽  
Development Projects ◽  
Software Development Project ◽  
Multiple Factors ◽  
Mining Tools ◽  
Software Team

The formation of software development project teams is carried out, conventionally, in an empiric manner; however, in this process, multiple factors should be considered. In literature, the works where this process is modeled are scarce, and most do not consider aspects linked to the formation of the team as a whole. In this paper, a group of patterns that contribute to the formation of software development projects teams are identified through the use of the Delphi method, psychological tests, and data mining tools. The paper identifies patterns that are validated experimentally, while psychological characteristics in the process of software team formations are exemplified.

Identification of Patterns for the Formation of Software Development Projects Teams

2012 ◽  
pp. 177-188
Author(s):  
Margarita André Ampuero ◽  
María G. Baldoquín de la Peña ◽  
Silvia T. Acuña Castillo
Keyword(s):  
Data Mining ◽  
Software Development ◽  
Development Project ◽  
Psychological Tests ◽  
Project Teams ◽  
Development Projects ◽  
Software Development Project ◽  
Multiple Factors ◽  
Mining Tools ◽  
Software Team

The formation of software development project teams is carried out, conventionally, in an empiric manner; however, in this process, multiple factors should be considered. In literature, the works where this process is modeled are scarce, and most do not consider aspects linked to the formation of the team as a whole. In this paper, a group of patterns that contribute to the formation of software development projects teams are identified through the use of the Delphi method, psychological tests, and data mining tools. The paper identifies patterns that are validated experimentally, while psychological characteristics in the process of software team formations are exemplified.

scholarly journals TESTING PROCESS OVERVIEW EXPLORATION FOR A SOFTWARE PRODUCT IN A LARGE SOFTWARE DEVELOPMENT PROJECT

2013 ◽  
pp. 100-105
Author(s):  
SRIHARSHA G ◽  
NARESH E
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Test Case ◽  
Test Cases ◽  
Software Development Project ◽  
Root Cause ◽  
Software Product ◽  
Large Software ◽  
Manual Test

Software testing is a process where you have the stated requirements, pre-requisite software that is to be installed and the configuration of the machine that need to be done as per the test data for the test case and for a specific platform which when verified works perfectly. This paper describes about Manual test case process overview in the testing life cycle for a large software development project and how you track the effort for the same. A Tester need to know about the fundamentals of testing concepts. Documentation of the testing concepts and the process overview of the testing life cycle for a software product need to be done initially so that a new tester when recruited can understand the basic flow as to how it is carried out in real time in an organization practically. Initially a tester need to execute the manual test case for few platforms and some tougher manual test cases need to be learnt from the tester who is having some experience. The tougher manual test cases need to be identified initially from the experienced tester who will be giving a session for the execution of such test cases. So when the foundation for a new tester is powerful the plan assigned for the execution of test cases is met. The effort tracking for the testing can be captured for a tester and should be matched with planned effort for the execution of test cases. Measurement of the testing effort plays a very important role as to how comfortable a new tester is and further root cause analysis is done if required when the new tester does not meet the planned effort.

scholarly journals Most severe risk factors in software development projects in Kuwait

2021 ◽  
Vol 21 (1) ◽  
pp. 591
Author(s):  
Abdullah J. Al-Shehab ◽  
Thalaya Alfozan ◽  
Hesham Gadelrab
Keyword(s):  
Risk Factors ◽  
Software Development ◽  
Quantitative Methods ◽  
Developed Countries ◽  
Development Project ◽  
High Rate ◽  
Development Projects ◽  
Face To Face ◽  
Software Development Project ◽  
Private Organizations

<p><span>Software development projects are famous of high rate failure, this made an encouragement for researcher to investigate reasons of failure. However, literature covering under developed countries is uncommon. This research investigates the most severe risk factors in software development project in the country of Kuwait. A face-to-face questionnaire with 109 IT practitioners in Kuwait from government and private organizations was conducted. The findings reveal and identify risk factors that have a high impact on the budget, quality, and schedule. The aim of this study is to validate risk factor taxonomy through quantitative methods by experts in the field of IT. Another purpose of this research is to provide a comprehensive and updated review of risk factors from Kuwait to be presented for IT practitioners and researchers.</span></p>

Risk Management in Software Development Projects

2020 ◽  
Vol 11 (1) ◽  
pp. 1-22
Author(s):  
Karollay Giuliani Oliveira Valério ◽  
Carlos Eduardo Sanches da Silva ◽  
Sandra Miranda Neves
Keyword(s):  
Risk Management ◽  
Software Development ◽  
Business Strategy ◽  
Development Project ◽  
Development Projects ◽  
Software Development Project ◽  
Vos Viewer ◽  
Close Relationship ◽  
Innovation Sector ◽  
New Strategies

Effective risk management contributes to the success of the software development project. The goal of this work was to identify risk management gaps, perspectives, the evolution of the theme and the study trends, in software development projects, using systematic literature review as a method. For the bibliometric analysis, articles referring to the topic were selected in the period from 2010 to 2018. As tools of analysis, Citespace and VOS Viewer software were used, allowing a comparative evaluation between the articles, as well as the analysis of clusters. Beyond content analysis of articles found. Gaps were identified for performance; team involvement; attention to failures; identification of tools for decision-making; and business strategy. In turn, perspectives were determined for research trends, such as the close relationship between business strategy, risk management and new management models. The research can propose new strategies and perspectives for risk management in software development and show their importance to the academic and practical spheres, demonstrating that the themes are complementary and important in the current technological and innovation sector.

scholarly journals A STEP TOWARDS LIGHT—LIFE CYCLE GLOBAL HYPERTEXT

1994 ◽  
Vol 05 (05) ◽  
pp. 765-766
Author(s):  
JULIAN BUNN ◽  
PAOLO PALAZZI ◽  
BERTRAND ROUSSEAU ◽  
MATTHIEW SMITH
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Source Code ◽  
Information Access ◽  
Development Project ◽  
Requirements Specification ◽  
Software Life Cycle ◽  
Analysis And Design ◽  
Software Development Project ◽  
Specification Analysis

Life Cycle Global HyperText offers easier information access to all members of a software development project, with all documents resulting from the software life cycle being available through WWW hypertext. These documents are connected, via hypertext links, to the documents produced in other stages of the life cycle. To experiment with this concept we have developed converters that transform several kind of documents into the WWW format. Up to now we have focused on source code, but we are now concentrating on documents produced in earlier stages of the software life cycle, such as requirements specification, analysis and design.

Knowledge Management and Quality Control in Software Outsourcing Projects

2017 ◽  
Vol 13 (4) ◽  
pp. 31-55 ◽  
Author(s):  
Rajorshi Sen Gupta
Keyword(s):  
Quality Control ◽  
Knowledge Management ◽  
Intellectual Property ◽  
Software Development ◽  
Service Providers ◽  
Economic Incentives ◽  
Development Project ◽  
Apparent Paradox ◽  
Software Development Project ◽  
Lump Sum

This article describes how entrepreneurs face critical risks in terms of quality control and knowledge management while outsourcing software development to independent service providers. First, it is recommended that lump-sum payment contracts should be avoided since software development project involves uncertainty. Instead, a variable payment contingent on observed quality can induce the service provider to exert optimal effort on the project. Second, entrepreneurs must not overlook the importance of providing economic incentives. They can protect their intellectual property by withholding critical knowledge and paying information rents in terms of higher than market wages to the service providers. Third, a startling result is that a low wage nation is not necessarily the optimal location to outsource software development projects. Thus, high wage-strong IPR nations might be chosen instead of low wage-weak IPR nations. Finally, the article explains the apparent paradox that software projects are often outsourced to locations that are characterized by weak intellectual property rights regime and high propensity of imitation.

Sign in / Sign up

Export Citation Format

Share Document