Cross-factor analysis of software engineering practices versus practitioner demographics: An exploratory study in Turkey

Garousi, Vahid; Coşkunçay, Ahmet; Demirörs, Onur; Yazici, Ali

doi:10.1016/j.jss.2015.09.013

Cited by 14 publications

(11 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Among our plans for future work directions are the followings: (1) to conduct semistructured interviews to get more in-depth insights about the high ranked CSFs; (2) investigation of low ranked factors, e.g., software development methodology and other project factors, which were quite disregarded in both our study and also in (Ahimbisibwe et al 2015); and (3) conducting cross-factor analysis (as we did in (Garousi et al 2016e)) to consider factors such as role, experience, holding certifications, and target sector of respondents when analyzing CSFs. It may be interesting to study if these variables had an influence on CSFs.…”

Section: Discussionmentioning

confidence: 99%

Correlation of critical success factors with success of software projects: an empirical investigation

et al. 2018

Self Cite

View full text Add to dashboard Cite

Software engineering researchers have, over the years, proposed different critical success factors (CSFs) which are believed to be critically correlated with the success of software projects. To conduct an empirical investigation into the correlation of CSFs with success of software projects, we adapt and extend in this work an existing contingency fit model of CSFs. To archive the above objective, we designed an online survey and gathered CSF-related data for 101 software projects in the Turkish software industry. Among our findings is that the top three CSFs having the most significant associations with project success were: (1) team experience with the software development methodologies, (2) team's expertise with the task, and (3) project monitoring and controlling. A comprehensive correlation analysis between the CSFs and project success indicates positive associations between the majority of the factors and variables, however, in most of the cases at non-significant levels. By adding to the body of evidence in this field, the results of the study will be useful for a wide audience. Software managers can use the results to prioritize the improvement opportunities in their organizations w.r.t. the discussed CSFs. Software engineers might use the results to improve their skills in different dimensions, and researchers might use the results to prioritize and conduct follow-up in-depth studies on those factors.

show abstract

Section: Discussionmentioning

confidence: 99%

Correlation of critical success factors with success of software projects: an empirical investigation

et al. 2018

Self Cite

View full text Add to dashboard Cite

show abstract

“…-LS03: Use probabilistic sampling: If researchers aim is to generalize to a target population, then probabilistic sampling must be considered [35]. -LS04: Use of convenience sampling: Garousi et al [21] describe the motivation for researchers selecting convenience sampling over other techniques, highlighting that convenience sampling is less expensive and troublesome. -LS05: Evaluate the trustworthyness of the sample [55]: Different ways for calculating the sample size depending on the size of the population have been proposed [32].…”

Section: Problems and Strategiesmentioning

confidence: 99%

“…[25] have used customized reports along with third party advertising to increase their response rate. -LS16: Use snowball sampling: Respondents of the survey are asked to answer and forward it to their colleagues [21][20]. -LS17: Recruit respondents from GitHub: Testers and coders can be recruited for a survey using GitHub [7][25].…”

Section: Problems and Strategiesmentioning

confidence: 99%

Survey Research in Software Engineering: Problems and Mitigation Strategies

et al. 2019

View full text Add to dashboard Cite

Background: The need for empirical investigations in software engineering is growing. Many researchers nowadays, conduct and validate their solutions using empirical research. Survey is one empirical method which enables researchers to collect data from a large population. Main aim of the survey is to generalize the findings. Aims: In this study we aim to identify the problems researchers face during survey design, and mitigation strategies. Method: A literature review as well as semi-structured interviews with nine software engineering researchers were conducted to elicit their views on problems and mitigation strategies. The researchers are all focused on empirical software engineering. Results: We identified 24 problems and 65 strategies, structured according to the survey research process. The most commonly discussed problem was sampling, in particular the ability to obtain a sufficiently large sample. To improve survey instrument design, evaluation and execution recommendations for question formulation and survey pre-testing were given. The importance of involving multiple researchers in the analysis of survey results was stressed. Conclusions: The elicited problems and strategies may serve researchers during the design of their studies. However, it was observed that some strategies were conflicting. This shows that it is important to conduct a trade-off analysis between strategies.

show abstract

“…In literature, quality, productivity and effort are also evaluated in terms of team familiarity, team structure with TS as a control variable (Huckman et al , 2009). Garousi et al (2016) conducted an exploratory study on individual experience along with project related factors, i.e. target industry, project size, CASE tools, and found an indirect impact on productivity.…”

Section: Research Synthesismentioning

confidence: 99%

Analyzing time pressure for software economics

Razzaq

Huang

Sun

et al. 2019

JEIM

View full text Add to dashboard Cite

Purpose The research on people and project factors is found extensively in general but not specific to software engineering. Secondly, the existing research has not concentrated on the communication and time complexity of the teams on software economics. The purpose this paper is to develop a model to investigate and quantify the impact of time pressure (TP) on software economics through the communication influence of software team sizes (TS). Design/methodology/approach A research model and five hypotheses are developed based on the gaps in the literature. The data set from International Software Benchmarking Standards Group repository is used for testing the hypotheses. Findings Important findings include: smaller TS tends to exert less TP on average; TP is directly proportional to software economics, however; and TP does not affect the productivity required for the software. Research limitations/implications The study has the following implications: Selection of an appropriate TS for project completion that ensures minimum pressure on team members; and maximize software outcomes in stress-free environment. Practical implications This work is useful for organizations carrying out software projects with teamwork. The project managers can benefit from the results while planning the team factors for achieving the project goals. Social implications The results uphold not to exert pressure on the team as it will not only affect the duly completion of the project but also the well-being of employees. Originality/value The paper is the first one where the proposition of TP estimation is done using TS and communication complexity, and empirically evaluating the impact of TP on four major software economics are the major key contributions of this research work.

show abstract

Cross-factor analysis of software engineering practices versus practitioner demographics: An exploratory study in Turkey

Cited by 14 publications

References 32 publications

Correlation of critical success factors with success of software projects: an empirical investigation

Correlation of critical success factors with success of software projects: an empirical investigation

Survey Research in Software Engineering: Problems and Mitigation Strategies

Analyzing time pressure for software economics

Contact Info

Product

Resources

About